X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=J7H
	0jvigZcc7YEIvO8IKvtWBXmKMmmBNDMc+I4nA0w9coy0loHOJbWsZhBm8j9UB952
	Ua+40RVbWg+kfJd/Ou6GRXOO+RsU25pHIxr4lJLwwuGJaBu9ZfExoekEYxX7xHZC
	E9IUPAijWWSWELQ7YLAarGmhHDd9XMZCWu97QB6o=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; s=default; bh=d6dmIs/YX
	fAB6MHSt5sbFDrPpzM=; b=HZiOPO63VcRYgrmv2H4kT3AgDt9PUw7/G83ooaTDC
	fkCNlgHVzK3bw0f/H2T/8JpUAtGlr3gjFbJgug+lJRPhmql443DPSrKekXGxAatf
	CCTTz0jLZoss+ahKMn3YSmYaW0EEuIy0ykLq3QrViGPDH7ctKzjWliQwyC7Ax+Nr
	7E=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-0.2 required=5.0 tests=AWL,BAYES_40,RDNS_NONE autolearn=no version=3.3.1
Message-ID:	<51EE9D94.6020904@isti.com>
Date:	Tue, 23 Jul 2013 11:13:24 -0400
From:	Stefan Lisowski <s DOT lisowski AT isti DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Upgrade Challenges, ssh login failure after update

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.

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

- Raw text -