On Tue, May 5, 2009 at 2:11 AM, ERG Consultant wrote:
> I am fully aware of the security issues having already written several helper
> tools. Stating that a temp text file written to /tmp is a security hole is
> really stretching it a bit.
I didn't say it was a security hole. I said it opened
I am fully aware of the security issues having already written several helper
tools. Stating that a temp text file written to /tmp is a security hole is
really stretching it a bit.
NSTemporaryDirectory can't be used because there is no way to specify that path
in Packagemaker. I did indeed end
On Sat, May 2, 2009 at 5:07 PM, Fritz Anderson wrote:
> For most purposes, it's enough for the plugin to write what it has learned
> into /tmp, for one of the scripts to act on.
Do not use /tmp. Use NSTemporaryDirectory, which on Leopard is a
user-specific directory. Using /tmp opens up a class
On 30 Apr 2009, at 7:31 PM, Erg Consultant wrote:
How can I get my installer plugin to run with the same admin
permissions as my installer runs with?
You can't. Plug-ins work as part of the Installer.app application,
which always runs with the privileges of the user who started it.
Privil
On 1 May 2009, at 01:31, Erg Consultant wrote:
I am using PackageMaker 2.1.1 from Xcode 2.5. My installers have to
work with 10.4/10.5.
My built installer prompts for an admin password before install, but
if my installer plugin tries to do any file operations on anything
inside /Applicati
