On Oct 2, 2008, at 9:30 PM, Kelly Graus wrote:
Hi Bill,Thanks for the response!This is the intended functionality. We are allowing a user to install system-wide content to our application. We also have the ability for users to install content for a single user with admin privileges.
Ah... OK. That makes sense and is a reasonable use case (i.e. what bug the heck out of users all the time :).
It is also a problem that has been addressed a number of times.As someone mentioned, can you use an installer package? pkgs can require authentication.
As well, the previously mentioned authopen could be used to write files with authorization.
This: http://developer.apple.com/documentation/Security/Conceptual/SecureCodingGuide/Articles/AccessControl.html And this: http://developer.apple.com/documentation/Security/Conceptual/authorization_concepts/02authconcepts/chapter_2_section_8.html Seem to be a good starting point. However, this document seems to potentially address your needs:http://developer.apple.com/documentation/Security/Conceptual/authorization_concepts/03authtasks/chapter_3_section_4.html#/ /apple_ref/doc/uid/TP30000995-CH206-TPXREF33
b.bum
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
