FROM : Sheehan Olver
DATE : Thu Dec 19 23:16:59 2002
Hmm, I see your point, but it still seems a bit hackish to copy the
applet to Application Support and run it from there. Sure, 99% of the
time there won't be a problem, but I'm sure there are certain
situations dealing with privileges that could be missed. Could there be
some way to leverage Key Chain support so they don't have to type the
password all the time?
On Thursday, December 19, 2002, at 03:29 PM, Peter Sichel wrote:
>> Couldn't you just copy the applet from your .app bundle to /tmp
>> whenever you run, and delete it when you quit? This way you don't need
>> to worry about permissions (/tmp is guaranteed everyone-readwrite,
>> correct?) Why do you need write access on an applet anyways?
>
> One of the reasons for isolating functions in an applet is to
> isolate root privileges to as little code as possible.
>
> How does the applet acquire root privileges?
>
> (A) Have the application ask the user every time?
>
> (B) Be set to SUID root at "first run installation time"
>
> I would argue that (B) is less intrusive and more secure than
> (A) which trains the user to casually authenticate applications.
>
> - Peter
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
DATE : Thu Dec 19 23:16:59 2002
Hmm, I see your point, but it still seems a bit hackish to copy the
applet to Application Support and run it from there. Sure, 99% of the
time there won't be a problem, but I'm sure there are certain
situations dealing with privileges that could be missed. Could there be
some way to leverage Key Chain support so they don't have to type the
password all the time?
On Thursday, December 19, 2002, at 03:29 PM, Peter Sichel wrote:
>> Couldn't you just copy the applet from your .app bundle to /tmp
>> whenever you run, and delete it when you quit? This way you don't need
>> to worry about permissions (/tmp is guaranteed everyone-readwrite,
>> correct?) Why do you need write access on an applet anyways?
>
> One of the reasons for isolating functions in an applet is to
> isolate root privileges to as little code as possible.
>
> How does the applet acquire root privileges?
>
> (A) Have the application ask the user every time?
>
> (B) Be set to SUID root at "first run installation time"
>
> I would argue that (B) is less intrusive and more secure than
> (A) which trains the user to casually authenticate applications.
>
> - Peter
_______________________________________________
cocoa-dev mailing list | <email_removed>
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 mail archive

