SABnzbd Forums

CPU: MacMini 3,1 - 2.26GHz - 4GB
OS: Mac OS X 10.7.4
SABnzbd: 0.7.0
IP: IPv4, using the local IP address

Extra info: Firewall: ON, Automatically allow signed software to receive incoming connections: ON, other settings: OFF.

Problem: Each time when SABnzbd starts after log-in, Mac OS X asks permission from an administrator to allow SABnzbd to accept incoming connections. This is then set to 'allow' in the firewall settings, but after the next log-in the system asks to set them again

Cause: Although the SABnzbd software is signed, shows that "a sealed resource is missing or invalid" which means that the source has been changed after initial signing. After the first execution more is changed.

Possible Solution: Use /Library/Application Support/SABnzbd/lib/ instead of /Applications/SABnzbd.app/Contents/Resources/lib/ to store and change python resources. The source can contain a hard link to that location, so it doesn't have to change. Another option is to use ~/Library/Application Support/SABnzbd/lib/.

-- This has been tested with an upgrade from 0.6.x and with a clean install in Mac OS X.

Interesting. I thought we solved this some time ago.
There was one stock Python file that kept being re-compiled after each run.
Needless to say that we don't test against OSX firewalls, maybe we should.
I'll see what I can do, but py2app seems to have a will of its own

BTW: the right solution is not to put part of the program in the profile.
I think that defeats the purpose of signing. You want to be certain that the app hasn't been tampered with.
How can you when part of it is stored in a user location?
An app should not be self-modifying and we did our best to separate code from data.
The Linux and Windows distros pull it off and so should the OSX one.

shypike wrote:Interesting. I thought we solved this some time ago.
There was one stock Python file that kept being re-compiled after each run.
Needless to say that we don't test against OSX firewalls, maybe we should.

... or promote Norbertus to be a release tester, and let him do the tests ...

There's an easy fix.
I just need to remove all .py files (except two) from the distribution (before signing).
I guess this is an anomaly of py2app: for some reason the Cheetah and xml module sources are
included, while none of the other modules include sources.
The presence of .py files makes Python want to touch the corresponding .pyc files.