Re: adding an executable as a resource
Re: adding an executable as a resource
- Subject: Re: adding an executable as a resource
- From: Markus Hitter <email@hidden>
- Date: Fri, 9 Dec 2005 18:45:01 +0100
Am 09.12.2005 um 17:45 schrieb Daniel Jalkut:
I wonder if anybody has any "advice from the trenches" about
possible snafus with regard to permissions going wrong on dependent
executables, etc. I suppose it's just as unlikely as the
permissions going wrong on your application's executable itself,
but it's "one more thing" to potentially go wrong.
You'd have a hard time to construct a scenario where the executable
bit of the helper tool gets erased but other permissions remain
intact. It's not "one more thing", it's the same thing: permissions
have to be preserved across copies.
Any horror stories?
Some apps try to store stuff inside their app's bundle, making it
impossible to run the app off a CD or a read-only network share or a
read-only disk image.
Other apps liberately set the suid bit to on, permissions to
rwxrwxrwx and the owner to "root" as well, pushing doors wide open
for root kits.
Two examples of intended misbehaviour, the defaults do better.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
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