Re: Modifying system files
Re: Modifying system files
- Subject: Re: Modifying system files
- From: Shawn Erickson <email@hidden>
- Date: Sat, 09 Jun 2007 07:26:15 -0700
To echo what Wain stated... DO NOT modify files under /System unless
it is required as part of an Apple approved / supported pathway (aka
install KEXTs, etc.). If you still feel you need to do this you must
fully understand the security and stability issues involved and you
must inform your customers of what you are doing. You must take extra
care in implementing you software so that it itself or by way of what
it modifies doesn't expose or become a vulnerability. This means
fully understanding how to utilize authorization services, how to
install your application securely, how to keep it secure, and also
how to ensure you keep proper file permission, etc. on the files you
modify.
Additionally you will be modify files that Apple is free to rename,
change the format of, etc. on a whim because they are not part of the
public API for Mac OS X. You expose your customers up to all kinds of
potential issues with every security update, patch release, and major
revision.. and open yourself up to a possibly bad support situation.
Personally somethings just shouldn't be done even if you and your
customers think it would be a cool thing... I rate this type of
product as one of those.
-Shawn
On Jun 9, 2007, at 2:16 AM, Wain Glaister wrote:
Hi,
Your looking for authorization or authentication - BUT, you should
endeavour not to modify system files if there is another way to
achieve your goal.
http://www.google.co.uk/search?q=cocoa+authorization
http://developer.apple.com/documentation/Security/Conceptual/
authorization_concepts/01introduction/chapter_1_section_1.html
Wain
www.tekuris.com
On 9 Jun 2007, at 10:04, Aaron Wallis wrote:
Hi there,
I'm building an app similar to CandyBar which needs to modify
system files to customize the OSX user interface.
I'm using NSFileManager to do the modifications (as per this code):
NSFileManager * tFileManager = [[[NSFileManager alloc] init]
autorelease];
[tFileManager removeFileAtPath:tfilePath handler:self];
[tFileManager movePath:[NSString stringWithFormat:@"%@/
temp.aif", [bundleResource resourcePath]] toPath:tfilePath
handler:self];
when it attempts to remove the file, it throws a "Error Removing"
error, and obviously, doesn't remove the file...
I know, with the likes of candy bar, it asks for authentication to
make the changes before doing whatever it does, but I can't seem
to find any documentation on how to request for the user to login
or such...
Any ideas?
Cheers :D
- Az
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
40tekuris.com
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden