This is the mail archive of the
mailing list for the Cygwin project.
Re: Filtered tokens
On Tue, Apr 27, 2010 at 9:26 AM, Corinna Vinschen
> 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.
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. ?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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple