X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=BAYES_00,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: <20100427135804.GH1845@calimero.vinschen.de> References: <20100427091011 DOT GB12365 AT calimero DOT vinschen DOT de> <20100427132614 DOT GG1845 AT calimero DOT vinschen DOT de> <20100427135804 DOT GH1845 AT calimero DOT vinschen DOT de> Date: Tue, 27 Apr 2010 10:14:41 -0400 Message-ID: Subject: Re: Filtered tokens From: Patrick Julien To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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:58 AM, Corinna Vinschen wrote: > On Apr 27 09:33, Patrick Julien wrote: >> On Tue, Apr 27, 2010 at 9:26 AM, Corinna Vinschen >> 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. =A0Creating our own session for eac= h 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. =A0A session can only be created by a trusted logon process. > There isn;'t a simple API to request a new session ID. =A0Additionally, > on client machines RDP only allows one user RDP session. =A0If, say, an > ssh login would request a session, the request would either be refused, > or it would lock the console window. =A0Only on real RDP servers you can > have multiple sessions. I am going to research this a bit and see if anything can be done. When UAC prompts the user, you have switched session so there has to be a way to do it. > >> > That's because setup works that way. =A0If you want the ownership of t= he >> > 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. =A0See the original post, any program can read/write to >> any executable in cygwin without escalation because I'm the owner. > > No, it isn't. =A0If you're admin you have this right anyway and non-admin > users still have restricted access to the files. =A0Just because UAC > exists, it's not automatically a good concept. > I don't want to start debating the good or bad of UAC, but if setup would just assign the owner to be 'system' instead of the admin user who started setup, when I run a command line as that user, I wouldn't have write access from inside cygwin. I would need to start the cygwin environment elevated to do that. -- 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