Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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 (, deleting sshd-keygen-wrapper, rebooting and saying yes to ssh-keygen-wrapper (though it was already set to yes) seems to work. – Dan Rosenstark Apr 2 '11 at 20:27

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/

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 – Dan Rosenstark 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

The commands below worked for me on Yosemite

cd /usr/libexec/ApplicationFirewall
sudo ./socketfilterfw --setloggingmode on
sudo ./socketfilterfw --setloggingopt detail
sudo tail -f /var/log/appfirewall.log

Try to connect to your Mac over SSH. You should see a deny entry, in my case sshd-keygen-wrapper

Oct 27 15:22:12 myhost socketfilterfw[4940] <Info>: Deny sshd-keygen-wrapper connecting from to port 22 proto=6

Then simply add /usr/libexec/sshd-keygen-wrapper (as suggested by mehaase) to the list of allowed applications, but there is no need to reboot

To switch the logging level back

./socketfilterfw --setloggingopt throttled
share|improve this answer

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

I found the idea here:

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

share|improve this answer

In El Capitan 10.11.5, sshd-keygen-wrapper was in the list of allowed connections, but was set to block. It was only necessary to set it to allow, and remote SSH login worked. No reboot required.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .