This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Filtered tokens
On Tue, Apr 27, 2010 at 9:58 AM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Apr 27 09:33, Patrick Julien wrote:
>> On Tue, Apr 27, 2010 at 9:26 AM, Corinna Vinschen
>> <corinna-cygwin@cygwin.com> wrote:
>> > On Apr 27 08:39, Patrick Julien wrote:
>> >> OK, I understand why it's the privileged token but why is it still in session 0?
>> >
>> > Because it's started in session 0. ?Creating our own session for each user
>> > could result in an enormous memory leak.
>>
>> That's how the regular logon does it, don't see why it has to leak.
>
> I meant in case of an error but, never mind.
>
> The basic problem is that Cygwin doesn't constitute a remote desktop
> logon server. ?A session can only be created by a trusted logon process.
> There isn;'t a simple API to request a new session ID. ?Additionally,
> on client machines RDP only allows one user RDP session. ?If, say, an
> ssh login would request a session, the request would either be refused,
> or it would lock the console window. ?Only on real RDP servers you can
> have multiple sessions.
This is funny. UAC creates another session on prompt but it's
unlikely the call is documented because powershell "remoting" sessions
also run in session 0. I think this is funny because MSFT made such a
big thing of the work they did in Vista to move processes out of
session 0 from the console.
For the admin rights, I think it's low hanging fruit just to change
the default owner to system but whatever
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple