MIME-Version: 1.0
In-Reply-To: <20100427132614.GG1845@calimero.vinschen.de>
References: <g2w9bdf03d21004261234qb993397y3afa2e9c60bca60c@mail.gmail.com> 	 <20100427091011.GB12365@calimero.vinschen.de> 	 <n2t9bdf03d21004270539l392560b0h62d6bd9189f72a91@mail.gmail.com> 	 <20100427132614.GG1845@calimero.vinschen.de>
Date: Tue, 27 Apr 2010 09:33:46 -0400
Message-ID: <v2w9bdf03d21004270633z9ff58c81kb1faa503183272e9@mail.gmail.com>
Subject: Re: Filtered tokens
From: Patrick Julien <pjulien@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

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