Re: loading kext from a daemon program
Re: loading kext from a daemon program
- Subject: Re: loading kext from a daemon program
- From: Kevin Elliott <email@hidden>
- Date: Sun, 7 May 2006 09:11:04 -0700
At 13:02 +0200 on 5/6/06, Markus Hitter wrote:
Am 06.05.2006 um 11:51 schrieb Michael Smith:
why are the spawn family of interfaces so popular, if system(3) is so great?
system(3) is a convenience function for the more common cases of
spawning? I can't see a >stringent need to avoid this function
either.
Just to make this COMPLETELY explicit.
If you call system, then the launching user environment (that is, the
user and anyone who can alter his system) has complete control over
what your launch command actually does:
-He can point you at a different binary
-He can probably screw with your arguments
Yes, their is an argument that if the user enviroment can be modified
then the person is already screwed. But why make it any easier?
If fork/exec are a pain, then use one of the higher level API's!
Cocoa has a very nice one, and I believe Carbon does as well. System
is not the answer.
--
______________________________________________________
Arguing with an engineer is like wrestling with a pig in mud.
After a while, you realize the pig is enjoying it.
______________________________________________________
Kevin Elliott <mailto:email@hidden>
AIM/iChatAV: email@hidden (video chat available)
______________________________________________________
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden