Re: <no subject>
Re: <no subject>
- Subject: Re: <no subject>
- From: Dave Camp <email@hidden>
- Date: Tue, 5 Aug 2003 20:35:40 -0700 (PDT)
On Tue, 5 Aug 2003, Alec Carlson wrote:
>
This is the case. The app is launched as a Login item and is owned by the
>
user logging in. And I agree with you 100%, the second user should not be
>
affected by it. But the only way that can happen is if the background app
>
KNOWs there is another user using the system via a fast user switch. What I
>
am looking for is a way to make that determination.
As a login item owned by the user logged in, you have no rights to fiddle
with other users stuff (files, UI, or otherwise). That would be a security
violation.
If your app really needs to have access to all users files, it has to be a
StartupItem running as root, which has all sorts of security implications.
It's easy to have a mistake in your code that leaves the user vulnerable
to exploits.
Otherwise, your app should be blissfully ignorant of who the current UI
user is. It should not matter whose session is currently on the monitor.
If you need to do something for each user, each user should have a copy of
your app running.
I going to go out on a limb here and say that you're still getting
negative responses because you have not explained what exactly your app
does. All we know is that it's a background Login item owned by the user,
but it wants to interact with another users files, which would be
potentially major security violation. Can you give us more details as to
what your app does? I suspect there is something we are missing here that
is needed to help you.
Dave
_______________________________________________
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.
| References: | |
| | ><no subject> (From: Alec Carlson <email@hidden>) |