Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <40C05F95.7050207@ecs.soton.ac.uk>
Date: Fri, 04 Jun 2004 12:40:05 +0100
From: Andy Rushton <ajr1@ecs.soton.ac.uk>
Organization: Southampton University
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
MIME-Version: 1.0
To: Cygwin List <cygwin@cygwin.com>
Subject: Re: decoding sshd failure
References: <40BFDACD.4020104@machturtle.com> <6.1.0.6.0.20040603230705.032836e8@pop.theworld.com> <200406040638.42277.dcorbin@machturtle.com>
In-Reply-To: <200406040638.42277.dcorbin@machturtle.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Someone wrote:

>>>Below is a fragment of output from sshd -d -d -d
>>>
>>>Can someone tell me why it doesn't like my publickey?  I think I've done
>>>everything right, but no joy.  I can login using the password just fine.
>>>      
>>>
Sorry, I missed the start of this thread so I don't know who the 
original author is but I have some suggestions:

I had a problem with ssh not finding my .ssh directory. It turned out 
that ssh gets your home directory from /etc/passwd and not from $HOME 
and in my case, for perverse Windows-related reasons I don't understand, 
this was different. Editing /etc/passwd fixed it. Check the path that 
ssh is reporting that its looking in and check that this is the right place.

Also, I had an embarrassing error the first time I set this up - being 
British I spelt authorized_keys with an 's' not a 'z'. It took me a 
while to spot the problem.

You don't say what your directory structure is, so could one of these be 
the problem?

Andy

-- 
Andy Rushton, Southampton, UK

   Be careful or be road-kill.
		  -- Calvin


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