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: Fri, 26 Jul 2002 10:22:33 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Future ntsec-detection problem in sshd (Re: winsup/cygwin ChangeLog security.cc) Message-ID: <20020726102233.V3921@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20020725170413.3469.qmail@sources.redhat.com> <005d01c23417$27a656e0$0100a8c0@wdg.uk.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005d01c23417$27a656e0$0100a8c0@wdg.uk.ibm.com> User-Agent: Mutt/1.3.22.1i On Thu, Jul 25, 2002 at 09:09:16PM +0100, Max Bowsher wrote: > > CVS Log message: > > * security.cc (allow_ntsec): Default to on. > > A good idea, but I just want to mention a problem that will eventually arise > with sshd. > > It currently checks whether ntsec is enabled by examining the CYGWIN environment > variable. This means that if ntsec is defaulted to on, without ntsec appearing > in the CYGWIN env var, that code now requires reworking. The location of this > now-problematic code in ssh is check_nt_auth in file > openbsd-compat/bsd-cygwin_util.c. Thanks for the heads up. I have to add a version check then. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/