X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 27 Apr 2010 15:58:04 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Filtered tokens
Message-ID: <20100427135804.GH1845@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <v2w9bdf03d21004270633z9ff58c81kb1faa503183272e9@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 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.  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.

> > That's because setup works that way.  If you want the ownership of the
> > files being administrator, start setup as administrator.
> 
> Gee thanks, yeah, I got that, I still think it's a security issue,
> that is, a bug.  See the original post, any program can read/write to
> any executable in cygwin without escalation because I'm the owner.

No, it isn't.  If you're admin you have this right anyway and non-admin
users still have restricted access to the files.  Just because UAC
exists, it's not automatically a good concept.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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