Re: Distributed Objects communication with a launchd "on-demand" daemon
Re: Distributed Objects communication with a launchd "on-demand" daemon
- Subject: Re: Distributed Objects communication with a launchd "on-demand" daemon
- From: Jens Alfke <email@hidden>
- Date: Thu, 17 Dec 2009 08:48:33 -0800
On Dec 16, 2009, at 8:05 PM, Frank Rizzo wrote:
> I am trying to create a launchd daemon that is started "on-demand" by a
> client call to a TCP port number and then communicate with the client via
> Distributed Objects.
I would advise against this. IMHO it only makes sense to use DO if both sides of the connection are running code you wrote. There is no way to guarantee this if you use sockets, since anything could connect to the port your server listens on. A DO-based server has a lot of vulnerability to buggy or malicious code that sends it improper requests, so unless you are obsessive about bullet-proofing the code, it's very easy to confuse or crash the server. (And needless to say, that's much more dangerous if your daemon runs as root.)
I wrote a blog post about it a few months ago:
http://jens.mooseyard.com/2009/07/the-subtle-dangers-of-distributed-objects/
—Jens_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden