X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.8 required=5.0 tests=BAYES_20,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SARE_MSGID_LONG45,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<20100427135804.GH1845@calimero.vinschen.de>
References:	<g2w9bdf03d21004261234qb993397y3afa2e9c60bca60c AT mail DOT gmail DOT com> <20100427091011 DOT GB12365 AT calimero DOT vinschen DOT de> <n2t9bdf03d21004270539l392560b0h62d6bd9189f72a91 AT mail DOT gmail DOT com> <20100427132614 DOT GG1845 AT calimero DOT vinschen DOT de> <v2w9bdf03d21004270633z9ff58c81kb1faa503183272e9 AT mail DOT gmail DOT com> <20100427135804 DOT GH1845 AT calimero DOT vinschen DOT de>
Date:	Tue, 27 Apr 2010 10:44:06 -0400
Message-ID:	<y2y9bdf03d21004270744j34bab67cnfb6998273aec21b@mail.gmail.com>
Subject:	Re: Filtered tokens
From:	Patrick Julien <pjulien AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Tue, Apr 27, 2010 at 9:58 AM, Corinna Vinschen
<corinna-cygwin AT cygwin DOT com> wrote:
> On Apr 27 09:33, Patrick Julien wrote:
>> On Tue, Apr 27, 2010 at 9:26 AM, Corinna Vinschen
>> <corinna-cygwin AT cygwin DOT 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. =A0Creating our own session for eac=
h 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. =A0A session can only be created by a trusted logon process.
> There isn;'t a simple API to request a new session ID. =A0Additionally,
> on client machines RDP only allows one user RDP session. =A0If, say, an
> ssh login would request a session, the request would either be refused,
> or it would lock the console window. =A0Only 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

- Raw text -