public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gerry Reno <greno@verizon.net>
To: cygwin@cygwin.com
Subject: 1.7.7:  after upgrade lost ability to login via ssh
Date: Wed, 09 Feb 2011 02:14:00 -0000	[thread overview]
Message-ID: <4D51F868.6010000@verizon.net> (raw)

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
    debug1: match: OpenSSH_5.8 pat OpenSSH*
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_5.2
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: server->client aes128-ctr hmac-md5 none
    debug1: kex: client->server aes128-ctr hmac-md5 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    debug1: Host 'MACHINE_IP' is known and matches the RSA host key.
    debug1: Found key in /root/.ssh/known_hosts:49
    debug1: ssh_rsa_verify: signature correct
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: SSH2_MSG_SERVICE_REQUEST sent
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue:
    publickey,password,keyboard-interactive
    debug1: Next authentication method: publickey
    debug1: Trying private key: keypair1.pem
    debug1: read PEM private key done: type RSA
    debug1: Authentication succeeded (publickey).
    debug1: channel 0: new [client-session]
    debug1: Requesting no-more-sessions@openssh.com
    debug1: Entering interactive session.
    debug1: Sending environment.
    debug1: Sending env LANG = en_US.UTF-8
    Last login: Tue Feb  8 11:18:47 2011 from LOCAL_CLIENT_MACHINE
    debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
    debug1: client_input_channel_req: channel 0 rtype eow@openssh.com
    reply 0
    debug1: channel 0: free: client-session, nchannels 1
    Connection to MACHINE_IP closed.
    Transferred: sent 2224, received 2144 bytes, in 2.9 seconds
    Bytes per second: sent 764.9, received 737.4
    debug1: Exit status 0


The session looks like its connected ok but then it immediately
disconnects. 

Anyone else seen this on upgrade or have an idea how to fix this?



Regards,
Gerry




--
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

             reply	other threads:[~2011-02-09  2:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  2:14 Gerry Reno [this message]
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)
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=4D51F868.6010000@verizon.net \
    --to=greno@verizon.net \
    --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).