X-Spam-Check-By:	sourceware.org
Mime-Version:	1.0
Message-Id:	<p06240805c2d39a58a0f2@[192.168.1.8]>
In-Reply-To:	<46ADE970.7010000@Hipp.com>
References:	<p06240802c2d24b662020@[192.168.1.8]> <f8ite8$at$1 AT sea DOT gmane DOT org> <p06240801c2d2ab3c9626@[192.168.1.8]> <f8j7aq$qja$1 AT sea DOT gmane DOT org> <p06240802c2d2de2f403a@[192.168.1.8]> <f8jbjd$4uc$1 AT sea DOT gmane DOT org> <p06240804c2d3961da325@[192.168.1.8]> <46ADE970 DOT 7010000 AT Hipp DOT com>
Date:	Mon, 30 Jul 2007 09:40:39 -0400
To:	Michael Hipp <Michael AT Hipp DOT com>
From:	Daniel Griscom <griscom AT suitable DOT com>
Subject:	Re: sshd: public key working, but can't get passwords working
Cc:	cygwin AT cygwin DOT com
X-Antivirus-Scanner:	This message has been scanned by ClamAV.
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id l6UDeqXq027217

At 8:36 AM -0500 7/30/07, Michael Hipp wrote:
>Daniel Griscom wrote:
>>At 7:32 PM -0500 7/29/07, René Berber wrote:
>>>Back to the original problem: did you use ssh-user-config?  (I guess you did
>>>since you had to copy the public key).
>>
>>No; I'd thought that ssh-user-config was to 
>>configure an account that was to be an ssh 
>>client (e.g. one within which I'd use ssh to 
>>connect to another machine). I copied the 
>>public key from another workstation from which 
>>I've used ssh public key connections for a 
>>number of servers.
>>
>>>What you reported about the log is simple, the 
>>>password used is not correct...
>>>it should prompt you 3 times and then close 
>>>the connection; or the configuration
>>>does not allow password authentication, let's check this last one:
>>>
>>>In /etc/sshd_config you should have:
>>>
>>>#PasswordAuthentication yes
>>>#PermitEmptyPasswords no
>>>#UsePAM no
>>
>>All three lines are present and commented out (as above).
>
>I thought you were trying to use public/private 
>key authentication, not password authentication?

Sorry: public key works, and is great, but I'd 
also like the option of password authentication, 
and sshd always refuses my password.

>If so, then the first line above needs to be 
>uncommented and changed to 'no'.  (Remember to 
>keep a session open while you're testing 
>changes, and any changes won't become "live" 
>until sshd is restarted on the host.)
>
>I think you said you were using authorized_keys2 
>as the public key file, try using 
>~/authorized_keys (note the missing '2').

Has authorized_keys supplanted authorized_keys2? 
(I've always used the latter, and it's working in 
this situation, but perhaps I'm accumulating bad 
juju...)


Thanks,
Dan

--
Daniel T. Griscom             griscom AT suitable DOT com
Suitable Systems              http://www.suitable.com/
1 Centre Street, Suite 204    (781) 665-0053
Wakefield, MA  01880-2400

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -