Re: cocoa-dev digest, Vol 2 #3128 - 15 msgs
Re: cocoa-dev digest, Vol 2 #3128 - 15 msgs
- Subject: Re: cocoa-dev digest, Vol 2 #3128 - 15 msgs
- From: Stéphane Sudre <email@hidden>
- Date: Sat, 1 Nov 2003 11:23:02 +0100
On samedi, novembre 1, 2003, at 05:20 AM, Ryan McGann wrote:
On Oct 31, 2003, at 7:44 PM, email@hidden wrote:
It may not work, but you could try checking the owner of the
loginwindow or WindowServer processes. When logged in they're owned
by
the logged in user... presumably at the login screen they are owned by
root, or some other generic account.
Mac OS X has many security precautions to prevent the exact kind of
behavior you want.
(1) No process may make a connection to the WindowServer when
loginwindow is the front process. That means no AppKit framework, no
windows, nada. If your StartupItem links against any framework that
checks in with the WindowServer (like AppKit does) then it will be
killed before the loginwindow is ever shown.
A process can make a connection to the WindowServer when loginWindow is
the front process. You can have AppKit, windows, etc... You just have
to launch the process using LaunchServices for instance from a
bootstrap daemon. There was a security flaw in Retrospect due to this
behavior.
It's still working on Panther.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.