This is the mail archive of the
mailing list for the Cygwin project.
Re: Filtered tokens
On Apr 27 09:33, Patrick Julien wrote:
> On Tue, Apr 27, 2010 at 9:26 AM, Corinna Vinschen
> <firstname.lastname@example.org> 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 Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple