Re: Distributed Objects client/peer identification
Re: Distributed Objects client/peer identification
- Subject: Re: Distributed Objects client/peer identification
- From: Nicko van Someren <email@hidden>
- Date: Wed, 13 Feb 2008 08:51:32 +0000
On 12 Feb 2008, at 15:35, Adam R. Maxwell wrote:
On Feb 11, 2008, at 6:22 AM, Nicko van Someren wrote:
I have a background agent and a System Preferences panel to allow
the user to configure it. They talk to each other using
Distributed Objects. The Programming Topics for DO tells me that
the delegate of the NSConnection gets asked to confirm is a new
connection should be allowed.
What I want to do is determine what task is trying to make the
connection to my application. In particular, I want to be able to
make sure that the other end of the connection is a task belonging
to the same user (for instance because some other user is also
logged in using fast user switching).
Last time I tested something like this with fast user switching, a
program started by user A that registered under a given name was not
seen by user B (and B was able to launch the program and register it
with the same name). I'm using NSMachPort, and launching the
background programs with NSTask; if you use NSSocketPort and/or
launchd, things could be different.
Thanks, that is very helpful to know. I have however checked that one
user can, upon request, connect to a mach port belonging to another
user, so while we have natural name space separation we don't actually
have any protection.
Cheers,
Nicko
_______________________________________________
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