Annoying Firewall Allow / Deny Dialog

Me too, i wish apple fix this problem in Mac OS X 10.6.3 Update soon 😟

In the preferance pane Security -> Firewall -> Advanced I deleted all of my Allow/Block incoming connections (essentially starting over from scratch) and that solved the issue for me.

Does anyone have a viable answer to this yet?

I get the popup with firefox everytime I try to download something. I get it TWICE in a row everytime. So annoying when I am doing multiple downloads.

I don't want to turn my firewall off. This should be a very high priority fix for Apple because it is a ridiculous bug.

same problem here.
it started a couple months ago with JDownloader, and now Word, Excel and Powerpoint do it too.
i configured the firewall to always allow these apps, but they insist on asking.

Same with me too. Just updated to 10.6.3 and problem's still there.

I had also hoped that 10.6.3 would fix this, but unfortunately it hasn't. This is behavior we expect from Windows, not OS X.

Message was edited by: MadMacintosh

It does happen to me as well with many applications such as Dropbox, Skype, Vuze. I've tried everything, from removing com.apple.apl.plist to manually adding/removing allowed apps. Nothing worked, except *turning firewall off*, which I consider not to be the smartest solution. I think it's about time Apple solved that issue. Appreciate any other hints.

Same here (with SyncDocs and many other apps).
I've also configured the firewall to always allow these apps, but they insist on asking...
Useless firewall (rules) I guess?!

Apple, please take action.

exactly the same here.

mac os x 10.6.3
CLEAN install

aMSN and jDownloader keep prompting every time I start them.

it never worked.
not with 10.5 or any other version.

I think I figured it out:

http://support.apple.com/kb/HT1810

+If you run an unsigned application not in the Application Firewall list, you will be presented with a dialog with options to Allow or Deny connections for the application. If you choose Allow, Mac OS X 10.5 will sign the application and automatically add it to the Application Firewall list. If you choose Deny, Mac OS X 10.5 will sign the application, automatically add it to the Application Firewall list and deny the connection.+

+Some applications check their own integrity when they are run without using code signing. If the Application Firewall recognizes such an application it will not sign it, but then it will re-present the dialog every time the application is run. This may be avoided by upgrading to a version of the application which is signed by its developer.+

someguy2010,

if so, then I guess the only way to stop all these "allow/deny" is to simply turn off the firewall...
Not good, but better than being annoyed every time by it..

(seems we now only need an ""AppStore" for OSX, so then all the apps will stay signed..) 🙂

One thing to try. This appears to work for me, although I can't claim it's 100% reliable.

- in the firewall settings dialog box, select the application and delete it from the list.

- now run that application

- it reappears in thelist, but something about this seems to update the digital signature and the pop up no longer appears.

::: a different workaround is to select the "only core services" setting of the firewall and not set it individually for various apps. Can be supplemented for security with Lil Snitch.

Deleting the application from the Firewall list only seems to work for the first subsequent launch of the application.

App launches after that still pop up the window even with "Allow connections" for the app appearing in the Firewall list.

Hi!

I've been having the same problem with Vuze, having had to manually Allow each time when starting the program.

I think I managed to solve the problem following the (rather convoluted) procedure describe here: http://forums.macnn.com/79/developer-center/355720/how-re-sign-apples-applicatio ns-once/
"
However, I had to check the "Code signing" box at step 12 of "Obtaining a Code Signing Certificate" – thus not abiding with the defaults there. Also having completed the code signing part, I also removed Vuze from the Firewall's allowed list and re-entered it, although I don't know if it was necessary.

I probably will have to rerun the codesign command each time Vuze updates itself, but that shouldn't be so bad.

- Kalle

Hmmm still having this problem with 10.6.4