Currently Being ModeratedMay 16, 2013 3:01 PM (in response to ravs78)
Hi, did you unlock the lock when you chose that setting, then lock it after changing it?
Then there's a Terminal method to clear an App, #2 here...
Currently Being ModeratedMay 16, 2013 3:53 PM (in response to ravs78)
This can happen because an application has an invalid code signature, among other reasons. Follow the instructions linked below under the heading "How to open an app from a unidentified developer and exempt it from Gatekeeper."
Currently Being ModeratedMay 20, 2013 11:18 AM (in response to ravs78)
I've already tried the System Preference settings and still every time I open the application, I have to "accept" the Gatekeeper warning message.
FYI, it happens the same when the system is asking to accept or deny incoming connections, every time I open a an app, the system asks to accept/deny incoming connections. The firewall is properly set to accept incoming connections for the app.
I've repaired disk permissions as well, and nothing.
I've tried the Terminal method BDAqua suggested but I get the message:
"xattr: No such file: application_name"
I do not know if the following has something to do with this issue: I've once changed the user account name... of course, this new account has admin rights.
Currently Being ModeratedMay 20, 2013 2:40 PM (in response to ravs78)
sudo cp /var/db/.SystemPolicy-default /var/db/SystemPolicy
Currently Being ModeratedMay 22, 2013 1:44 PM (in response to Linc Davis)
Thanks... but it did not work :-/
Currently Being ModeratedMay 22, 2013 4:15 PM (in response to ravs78)
Are you installing the applications in the Applications folder, or are you running them from a disk image?
Currently Being ModeratedMay 23, 2013 8:47 AM (in response to Linc Davis)
All installed appliactions are on the Applications folder.
The samething happens with the Firewall setting, even if the application (XBMC) is set to allow incomming connections, and the system alsways asks the questino.
Currently Being ModeratedMay 23, 2013 11:12 AM (in response to ravs78)
codesign -vv /A*/XBMC* | open -f -a TextEdit
Currently Being ModeratedMay 23, 2013 12:46 PM (in response to Linc Davis)
here it is...
resource added: /Applications/XBMC.app/Contents/Resources/XBMC/addons/script.module.simplejson/ lib/simplejson/__init__.pyc
resource added: /Applications/XBMC.app/Contents/Resources/XBMC/addons/script.module.simplejson/ lib/simplejson/decoder.pyc
resource added: /Applications/XBMC.app/Contents/Resources/XBMC/addons/script.module.simplejson/ lib/simplejson/encoder.pyc
resource added: /Applications/XBMC.app/Contents/Resources/XBMC/addons/script.module.simplejson/ lib/simplejson/scanner.pyc
resource added: /Applications/XBMC.app/Contents/Resources/XBMC/addons/weather.wunderground/reso urces/lib/utilities.pyc
resource added: /Applications/XBMC.app/Contents/Resources/XBMC/addons/weather.wunderground/reso urces/lib/wunderground/wunderground.pyc
again... thanks a lot.
The firewall issue is with XBMC.
The Gatekeeper one is with Transmission (it does not happend with VLN for instance)
Currently Being ModeratedMay 23, 2013 2:19 PM (in response to ravs78)
In order for the application to be recognized by the firewall, it has to be codesigned. If it's codesigned by the developer with a certificate issued by Apple, the signature will be recognized automatically. Otherwise the signature has to be added by the firewall itself.
This particular application has an invalid signature because the compiled Python modules have changed when executed. Python is known for doing that. So what you need to do is remove the app from the allowed list and then add it back. That will generate a new signature.
I'm not familiar with Transmission, but something similar is probably happening.
Currently Being ModeratedMay 26, 2013 6:21 AM (in response to Linc Davis)
Thanks again but it's not working.
XBMC removed and re-added from the Firewall and nothing. It still asks to Accept or Deny incoming conenctions every time.
Concernning Transmission... I just intalled an updated version and the Gatekeeper question is not asked anymore
Do you think XBMC issue could be a similar problem: wait for an updated XBMC version?
Currently Being ModeratedMay 26, 2013 9:33 AM (in response to ravs78)
The only thing you can do to stop the warnings about XBMC is to change its ownership to root. You may have to do this with a fresh copy that hasn't already been codelsigned. Select it in the Finder and open the Info window. Click the lock icon on the lower right corner of the window and authenticate. Then, in the Sharing & Permissions section, give "System" read & write privileges and "Everyone" read-only privileges. Select Apply to enclosed items from the popup menu with the gear icon. Close the window and repeat the codesigning procedure.