Mac OSX Firewall Accept Incoming Connections Every Login
Posted: Sat Nov 03, 2012 4:49 amI had a problem where every time I logged in the OS asked if I wanted to "allow subsonic to accept incoming network connections", despite always choosing yes, having Subsonic in the allowed list, etc.
Turns out this is a problem with code signing. Here's the solution:
In terminal, type:
Then remove subsonic from the firewall list, turn firewall off, turn it back on, and add it again. I'm not sure if this last part is necessary, but it can't hurt
I forgot how I figured this out... I first did it a while ago and then again just tonight after upgrading to 4.7. I think the first hint was from a link on the Apple support forums about this (rather widespread) type of problem with the firewall, then some good ol' man-page reading for codesign. This is actually a relatively insecure way to deal with the problem, since the "-" after "-s" tells it to use an ad-hoc signature, which is a no-no, for whatever reason.
So if whoever builds the Mac binaries could take care of this, that would be great.
Turns out this is a problem with code signing. Here's the solution:
In terminal, type:
- Code: Select all
cd /Applications
sudo codesign -s - Subsonic.app -fv
Then remove subsonic from the firewall list, turn firewall off, turn it back on, and add it again. I'm not sure if this last part is necessary, but it can't hurt
I forgot how I figured this out... I first did it a while ago and then again just tonight after upgrading to 4.7. I think the first hint was from a link on the Apple support forums about this (rather widespread) type of problem with the firewall, then some good ol' man-page reading for codesign. This is actually a relatively insecure way to deal with the problem, since the "-" after "-s" tells it to use an ad-hoc signature, which is a no-no, for whatever reason.
So if whoever builds the Mac binaries could take care of this, that would be great.