Re: "First Run" installation of Application support stuff?
Re: "First Run" installation of Application support stuff?
- Subject: Re: "First Run" installation of Application support stuff?
- From: Michael Latta <email@hidden>
- Date: Wed, 18 Dec 2002 16:35:17 -0800
I am suspicious of any application that requires SUID, but for now I
will take your word for it that your users will support this
requirement.
Given that you have some secondary applications that require
parameterization, and you want a user other than root to be able to
provide that parameterization, I would suggest a system like this:
1) Place the CODE for the sub-applications under the app wrapper.
2) Place the parameter data in the user's pref area as usual.
3) Have the sub-applications accept a connection (pipe, etc.) to the
main program running in the user's context.
4) Have the sub-applications acquire their parameter data from the
user-based application.
The only time I could see any other approach would be that the
application is literally part of the OS and will never be used by other
than the root user. In that case it does not need to run as SUID and
can use the normal user preferences system.
Michael Latta
On Wednesday, December 18, 2002, at 01:18 PM, Peter Sichel wrote:
My application requires a bunch of small supporting applets that must
be configured as SUID root in order for the application to work.
I use the "First Run" process to complete the installation by
configuring these applets.
Question:
Should these applets remain inside the application bundle,
or be moved to "/library/Application Support/myApplication/..."
Notice leaving them inside the application bundle makes for
easy version control, install, and uninstall. The downside
is the need to modify the application bundle (will not work
from read only media), and the application bundle is not
easily copied from the Finder.
Moving these pieces to "/library/Application Support/myApplication/..."
makes for a less intuitive uninstall since the user is unlikely to
know which pieces belong to the application and introduces the problem
of managing file versions. What if the user has reason to use or test
more than one version of the same application? How does the
application
insure the correct version of its applets (plugins) are present without
conflicting with others? Especially since these applets are SUID root?
Opinions?
- Peter
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.