Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

If I turn on my OSX firewall, ssh is disallowed. If I turn it off, ssh can connect just fine. These are the settings from the ssh host: while I don't know what I'm doing, I figured that giving /usr/sbin/sshd "Allow Incoming Connections" (along with "Remote Login (SSH)") would be enough, but it's not. What else do I have to include for ssh (sshd? not sure) to allow connections?

The firewall configuration screen on OSX

I'm configuring ssh exclusively through the sharing menu, "Remote Login" in the System Preferences.

share|improve this question
    
As stated here (discussions.apple.com/thread.jspa?threadID=2174585), deleting sshd-keygen-wrapper, rebooting and saying yes to ssh-keygen-wrapper (though it was already set to yes) seems to work. –  Yar Apr 2 '11 at 20:27

2 Answers 2

I've seen this too - It seems that the OSX Application Firewall is getting confused. I managed to get mine going by doing the following:

sudo rm /Library/Preferences/com.apple.alf.plist

Then reboot.

Once the machine comes back up, when you go to Firewall > Advanced Settings, you should only see the system services you have enabled (in your case, SSH and Screen Sharing). The rest of the entries will have gone, but when you start any applications that need access through the firewall, OSX will ask you to permit the application or not again and should then be added back to the firewall exceptions list (if you allow it incoming connections).

share|improve this answer
    
Thanks, check my comment on the question too –  Yar Jan 16 '12 at 19:11
    
I found that if you run "sudo ipfw -f flush" and then close and re-open System Preferences, you can avoid the step of rebooting. –  mehaase Jul 11 '12 at 1:14

In my case, I added /usr/libexec/sshd-keygen-wrapper to the firewall settings and rebooted.

I found the idea here: https://discussions.apple.com/thread/2174585?threadID=2174585

One good troubleshooting technique: open Console.app and watch /var/log/appfirewall.log (or tail -f /var/log/appfirewall.log from the command line).

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.