Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 25 May 2005 15:24:53 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: "ssh-host-config -y" w/CYGWIN set to ntsec..; ssh works but CYGWIN *not* set Message-ID: <20050525132453.GD27399@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200505250445.j4P4jGmN029773@tigris.pounder.sol.net> <42940762.4FFDCE84@dessent.net> <429408C0.4070903@acm.org> <42940CC1.75E35408@dessent.net> <20050525081352.GB26571@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On May 25 09:08, Igor Pechtchanski wrote: > On Wed, 25 May 2005, Corinna Vinschen wrote: > > This is a change to sshd which had been requested upstream. The main > > developers felt that propagating all SYSTEM environment to the > > unprivileged child applications has to be treated as unsecure. > > Therefore I implemented to propagate only the core Windows environment > > to child processes back in 3.9, AFAIR. > > I would've thought that CYGWIN is a core environment variable (not a > Windows one, of course). I'm not sure, though, whether it would be > correct to propagate it -- one could argue either way... Right. The upcoming 4.1p1 release will propagate the CYGWIN variable as well. I just got that patch upstream last minute :-) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/