Re: AuthorizationExecWithPrivileges and /bin/cp
Re: AuthorizationExecWithPrivileges and /bin/cp
- Subject: Re: AuthorizationExecWithPrivileges and /bin/cp
- From: Scott Ellsworth <email@hidden>
- Date: Mon, 07 Nov 2005 14:44:24 -0800
On Nov 7, 2005, at 2:24 PM, Darkshadow wrote:
On Nov 7, 2005, at 3:55 PM, Cryptic Caveman wrote:
Basically, I want to run a tool (/bin/cp)
with root priviledges.
If you only make a call to AEWP, your users will have to authorize
every time that they need to use that functionality in your app.
If you use a setuid root tool, they'll only need to authorize once
(when the tool self-repairs itself), and afterwards it doesn't
require authorization.
In general, I prefer the first approach for things done less often
than daily. For daily tasks, I would rather auth once.
Oh, and if you decide to use a setuid tool, save it in the user's
Application Support folder. Things like this should really go
there in the first place, and if you do that then the user can move
the application around wherever they want without problems.
Be sure that this will survive movement between machines gracefully,
especially if they explicitly do or explicitly do not copy
Application Support.
Currently, the ~/library folder is not synced on a server machine,
but many admins have made it do so, in order to save email and the
like. I rather hope that Leopard will sync everything but the things
that just cannot be, like machine specific prefs, as more and more
apps are saving user data into ~/Library/Application Support, which
makes it hard as heck to back up all your user data.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden