Closing port 22

Question

Level 1

0 points

Closing port 22

I ran GRC's Shield's Up port scan and find that port 22 is open.
I'm running the OS X firewall in stealth mode so I'm uncertain why it's open.
I also run Little Snitch and can't find any applications that are trying to use port 22.
I'd appreciate some advise.
Thanks

Posted on May 13, 2009 5:24 PM

Reply

Answer 1

May 13, 2009 5:34 PM in response to lichmd

Jeff,

Port 22 is used for secure shell connections, etc. Do you have Back to My Mac turned on? I'm not sure if this is the port it uses, but it may be.

In any case, I don't think this is something to worry about. Keep in mind that any service you run from your computer will open up at least one port. While this makes you potentially visible, it doesn't necessarily make you prone to attack.

Scott

Reply

Answer 2

noice_T

Level 3

545 points

May 13, 2009 6:59 PM in response to lichmd

A little off subject, but if you are really concerned about safety, you should just get a router instead of relying on OSX software firewall. Having a router will help you stealth all your ports.

Reply

Answer 3

BobHarris

Level 9

57,071 points

May 13, 2009 8:09 PM in response to lichmd

Do you have System Preferences -> Sharing -> Remote Login enabled (aka ssh; secure shell)?

Reply

Answer 4

lichmd Author

Level 1

0 points

May 13, 2009 11:35 PM in response to BobHarris

Gents,

I have all sharing off.
I have Cyberduck installed, but inactive.
I'm currently out of the country and using the hotel wifi, so security s an issue for me.
Any other ideas?
Thanks

Reply

Answer 5

BobHarris

Level 9

57,071 points

May 14, 2009 1:22 AM in response to lichmd

Is GRC seeing you, or the hotel's Wifi router?

If your system preferences -> network IP address is 192.168. . or 10. .*. then you are behind the hotel's NAT router.

If your IP address is not of that pattern, then you could use a Terminal session and the commands netstat and lsof to find if the port is open and the offending application. See "man lsof" and "man netstat".

Reply

Answer 6

Tim Haigh

Level 7

24,198 points

May 14, 2009 6:54 AM in response to BobHarris

Further to Bob's post.

sheilds up will scan your WAN(public IP address) connection not your LAN connection.

Reply

Answer 7

nerowolfe

Level 6

13,090 points

May 14, 2009 12:25 PM in response to Tim Haigh

Tim Haigh wrote:
Further to Bob's post.

sheilds up will scan your WAN(public IP address) connection not your LAN connection.

Yes, and to add to this thread,

Run Network Utility.app
Check your local IP address under "Info"
Now, under Port Scan, enter your local IP and scan all ports up to 1024 or so.
These are the real ports you should be concerned with.

Reply

Answer 8

lichmd Author

Level 1

0 points

May 14, 2009 4:04 PM in response to nerowolfe

Thank gents,

that did it for me. I was perplexed why my increasingly draconian rules were not blocking port 22 during the scan, I should have realized it was the hotel's wan once I ran Shields Up on my iPhone and got the same results.
Cheers,
J

Reply

Answer 9

nerowolfe

Level 6

13,090 points

May 14, 2009 5:34 PM in response to lichmd

Jeff Jacques1 wrote:
Thank gents,

that did it for me. I was perplexed why my increasingly draconian rules were not blocking port 22 during the scan, I should have realized it was the hotel's wan once I ran Shields Up on my iPhone and got the same results.
Cheers,
J

IMO, there is absolutely nothing wrong with being cautious or, or in a new environment, overly cautious. Not doing so can possibly allow unpleasant and disturbing side effects. 🙂
Better safe than sorry, "they" say. I am a belt and suspenders guy myself.

Reply