DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type; q=dns; s=default; b=H9ult6JI4pdj/4qD
	ulwtjlsnXPTDDcxjTjdjBvDKkBWRlfzUDePLPxVrXmbCoDLkwDeODr59v3IlfsaP
	POaek/kfL8z0f45iO/++1L/Z6NZYsF6xatBXjHCSQnIAtnayX5i0KFT9ZyuVt29J
	SbUWDNxAkhrIgxe/SZXRbpoTmFU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: david AT adboyd DOT com (J. David Boyd)
Subject: Re: Upgrade Challenges, ssh login failure after update
Date: Tue, 23 Jul 2013 15:57:03 -0400
Lines: 39
Message-ID: <m9hiob9trqwg.fsf@W0144758.usac.mmm.com>
References: <51EE9D94 DOT 6020904 AT isti DOT com>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.1299999999999999 (Gnus v5.13) Emacs/24.3 (cygwin)

Stefan Lisowski <s DOT lisowski AT isti DOT com> writes:

> I just updated Cygwin to the latest version from one that had been
> installed in maybe 2009... old.
>
> During the update process there was a note to go to cygwin.com to see
> what had changed in the new version that might affect me, but in the
> "upgrade" or the "faq" area I could find nothing warning me about
> anything specific.
>
> I was installing this on a box 2000 miles away where I tunnel remote
> desktop through ssh. Thank goodness I took down the firewall before I
> rebooted, because ssh no longer worked after a reboot, and I had to
> make a direct remote desktop connection to the machine before I got
> ssh up and running.
>
> I'm sending this mail to warn other users trying to upgrade
> sshd... After the upgrade I got login failures even though sshd
> service was running. I Googled and Googled, but I couldn't find an
> answer; port was open, ssh was up, and ssh connections worked fine
> (even to the external IP) from the local cygwin ssh, but not from a
> remote ssh. Logging locally didn't help, ssh -vvv remotely didn't
> help. FINALLY I figured it out, it was that the USERNAMEs are now case
> sensitive!!! So "administrator" fails but "Administrator" succeeds. I
> read somewhere I can fix this now by going back and editing
> /etc/passwd, but I haven't tried that yet; right now I'm just happy to
> have my firewall back up and tunneling remote desktop through ssh
> again. (I did a ssh-host-config in the process of debugging but I
> don't think I needed to.)
>
> Since I couldn't find this answer I'm sending it now to the list,
> hopefully the next person that runs into this will find it.

Interesting.

I'd just always assumed that usernames have always been case
sensitive.  Just used to Linux more than Windows, I guess.

Glad you figured it out!


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