From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24128 invoked by alias); 9 Feb 2011 22:35:26 -0000 Received: (qmail 24064 invoked by uid 22791); 9 Feb 2011 22:35:25 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_YG X-Spam-Check-By: sourceware.org Received: from nm24.bullet.mail.ac4.yahoo.com (HELO nm24.bullet.mail.ac4.yahoo.com) (98.139.52.221) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Wed, 09 Feb 2011 22:35:18 +0000 Received: from [98.139.52.195] by nm24.bullet.mail.ac4.yahoo.com with NNFMP; 09 Feb 2011 22:35:16 -0000 Received: from [98.139.52.141] by tm8.bullet.mail.ac4.yahoo.com with NNFMP; 09 Feb 2011 22:35:16 -0000 Received: from [127.0.0.1] by omp1024.mail.ac4.yahoo.com with NNFMP; 09 Feb 2011 22:35:16 -0000 Received: (qmail 64969 invoked from network); 9 Feb 2011 22:35:16 -0000 Received: from [192.168.1.231] (reply-to-list-only-lh@108.7.36.4 with plain) by smtp115.biz.mail.re2.yahoo.com with SMTP; 09 Feb 2011 14:35:16 -0800 PST X-Yahoo-SMTP: Uu383n6swBCEN1G9up0WSnxbvN8fCPmk Message-ID: <4D5316A4.7080902@cygwin.com> Date: Wed, 09 Feb 2011 22:35:00 -0000 From: "Larry Hall \(Cygwin\)" Reply-To: cygwin@cygwin.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Remi/2.0.0.21-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: 1.7.7: after upgrade lost ability to login via ssh References: <4D51F868.6010000@verizon.net> <4D52131F.9060603@cygwin.com> <4D530D72.7000302@verizon.net> <4D531023.6070807@verizon.net> In-Reply-To: <4D531023.6070807@verizon.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-02/txt/msg00266.txt.bz2 On 2/9/2011 5:07 PM, Gerry Reno wrote: > On 02/09/2011 04:56 PM, Gerry Reno wrote: >> On 02/08/2011 11:07 PM, Larry Hall (Cygwin) wrote: >> >>> On 2/8/2011 9:14 PM, Gerry Reno wrote: >>> >>>> Something else I just discovered after upgrading to 1.7.7 is that I now >>>> have lost the ability to login via ssh. >>>> >>>> I have OpenSSH installed and running sshd as a service. Both password >>>> and keys accepted. But now neither means will work. >>>> >>>> # ssh -i keypair1.pem Administrator@MACHINE_IP >>>> Last login: Fri Feb 4 17:19:26 2011 from LOCAL_CLIENT_MACHINE >>>> Connection to MACHINE_IP closed. >>>> >>>> >>>> So I increased verbosity but did not see anything obvious. >>>> >>>> >>>> # ssh -v -i keypair1.pem Administrator@MACHINE_IP >>>> OpenSSH_5.2p1, OpenSSL 0.9.8k-fips 25 Mar 2009 >>>> debug1: Reading configuration data /etc/ssh/ssh_config >>>> debug1: Applying options for * >>>> debug1: Connecting to MACHINE_IP [MACHINE_IP] port 22. >>>> debug1: Connection established. >>>> debug1: permanently_set_uid: 0/0 >>>> debug1: identity file keypair1.pem type -1 >>>> debug1: Remote protocol version 2.0, remote software version >>>> OpenSSH_5.8 >>>> >>> Does reverting OpenSSH to 5.7 make a difference? >>> >>> >> Downgraded to 5.7: >> >> bash-4.1$ sshd --version >> sshd: unknown option -- - >> OpenSSH_5.7p1, OpenSSL 0.9.8r 8 Feb 2011 >> >> >> > From client: >> >> ssh -i keypair1.pem Administrator@MACHINE_IP >> Last login: Wed Feb 9 12:54:08 2011 from LOCAL_CLIENT_IP >> Connection to MACHINE_IP closed. >> >> >> Nope. Still have the same problem. Connection is made but immediately >> closes. >> >> >> > > I'm suspecting this is related to running Cygwin 1.7. > > In looking back though some notes I started having bash shell problems > after upgrading from 1.5 to 1.7. > > Now on 1.7 if I try to run bash as a login shell it just gets "Bad > address" or segfault errors and immediately exits the shell which also > probably affects 'ssh'. > > I don't remember having any bash problems when I was running Cygwin 1.5 > on this machine. My notes reflect screen copies showing bash able to > run as a login shell without any problem. Yep, that's the way we all run by default (see cygwin.bat). I agree that if you're having problems getting bash to behave, it's best to focus on that issue first. Your ssh problems may just be another symptom of the same thing. How about sending cygcheck output ()? There may be something helpful in that which someone on the list might pick up on. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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