Ask Different is a question and answer site for power users of Apple hardware and software. 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

That is, what files does it actually change? I am deploying a new version of an application on to multiple machines (100+) and when I test it on a machine, the "You do not have permission to use the application" box pops up, due to quite strict restrictions on the machine. If I click "Always Allow..." then everything works fine. However I do not wish to have to click this box on 100+ machines. Is there a command line alternative which can accomplish the same thing?

share|improve this question
up vote 1 down vote accepted

If you can't work out what "Always Allow" does, I would suggest running something like fseventer to see what OS X changes. If it hits a plist file then you'll be able to run defaults on it.

I'm assuming its probably in the (But not tested)

share|improve this answer
Thanks! Using fseventer I found that it edits /private/var/db/dslocal/nodes/Default/[user].plist which contains a master copy of – DanielGibbs Jul 7 '11 at 21:33

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.