From: "Larry Hall \(Cygwin\)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.7.7: after upgrade lost ability to login via ssh
Date: Wed, 09 Feb 2011 23:43:00 -0000 [thread overview]
Message-ID: <4D5326B2.7010203@cygwin.com> (raw)
In-Reply-To: <4D531B83.3080000@verizon.net>
On 2/9/2011 5:56 PM, Gerry Reno wrote:
> On 02/09/2011 05:35 PM, Larry Hall (Cygwin) wrote:
>> 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
>> (<http://cygwin.com/problems.html>)? There may be something helpful in
>> that which someone on the list might pick up on.
>>
>
> Ok, ran a new cygcheck and attached it.
OK, thanks. What went wrong with the first installation?
I notice that this is using TS. Can you try experiment with this machine
locally? Or perhaps just try:
<http://cygwin.com/faq-nochunks.html#faq.setup.setup-fails-on-ts>
--
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
next prev parent reply other threads:[~2011-02-09 23:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 2:14 Gerry Reno
2011-02-09 4:08 ` Larry Hall (Cygwin)
2011-02-09 21:56 ` Gerry Reno
2011-02-09 22:07 ` Gerry Reno
2011-02-09 22:27 ` Gerry Reno
2011-02-09 22:35 ` Larry Hall (Cygwin)
2011-02-09 22:56 ` Gerry Reno
2011-02-09 23:43 ` Larry Hall (Cygwin) [this message]
2011-02-10 0:21 ` Gerry Reno
2011-02-10 1:05 ` Gerry Reno
2011-02-10 1:22 ` Gerry Reno
2011-02-10 1:49 ` Gerry Reno
2011-02-09 10:54 ` Corinna Vinschen
2011-02-09 16:34 ` Gerry Reno
2011-02-09 16:54 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D5326B2.7010203@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).