X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.8 required=5.0 tests=BAYES_40,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:	<20100427132614.GG1845@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>
Date:	Tue, 27 Apr 2010 09:33:46 -0400
Message-ID:	<v2w9bdf03d21004270633z9ff58c81kb1faa503183272e9@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: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 se=
ssion 0?
>
> Because it's started in session 0. =A0Creating our own session for each u=
ser
> could result in an enormous memory leak.

That's how the regular logon does it, don't see why it has to leak.
Running in session 0 means it's possible for non-elevated users, i.e.,
users that aren't admins, just regular users, to launch shatter
attacks on services.

>
>> Also, it doesn't really explain why the files are all installed with
>> ownership set to me
>
> That's because setup works that way. =A0If 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.

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