Authorization without permanent setuid on helper
Authorization without permanent setuid on helper
- Subject: Authorization without permanent setuid on helper
- From: email@hidden
- Date: Wed, 19 Jan 2005 22:49:12 +0000
Are there any security repercussions with always "double running" a helper tool instead of setuid'ing its file on the first run? By "double running" I mean running it from the main app, having it authorize, and then having it run itself as setuid (essentially following AuthSample but skipping the ownership and permission changes on the file).
I know that it'll incur the overhead of an extra process every time, but for the purpose I have in mind, efficiency is not an issue and it would make the app more mobile (without leaving Application Support garbage behind, as MoreAuthSample's approach would do).
_______________________________________________
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