creating a Mac OSX installer so the installed app won't set off the firewall -


I am currently delivering an .app file to the people in my organization. I drag it into the form of authentication in the form of authentication, but every time users launch the program, they get a firewall alert (checking the app for the launch update - is very important for us). Because users are not administrators, they can not prove to remove messages. Will an MPKG-installed application fire the firewall in such a way that the end users will need an administrator to allow updates? Is there a post-install script that I can add to my app to configure the firewall? The ultimate goal for me is that the administrator has authenticated the installer to run. After the installation, the administrator will log out, the normal user will log in and run the application without any firewall warning.

Edit: I should mention that the minimum version is 10.5 in the organization, but that's fine if the solution has worked on Tiger too.

If you sign the app to the app, even if it's just a self-signed certificate Using, the user will be asked to accept the launch of the app only once. Subsequent updates, giving signature certificates are identical, will not trigger the direct.

More information is in this and it is in it.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -