Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From: David Corbin <dcorbin AT machturtle DOT com>
To: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: decoding sshd failure
Date: Fri, 4 Jun 2004 06:38:42 -0400
User-Agent: KMail/1.6.1
References: <40BFDACD DOT 4020104 AT machturtle DOT com> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040603230705 DOT 032836e8 AT pop DOT theworld DOT com>
In-Reply-To: <6.1.0.6.0.20040603230705.032836e8@pop.theworld.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200406040638.42277.dcorbin@machturtle.com>

On Thursday 03 June 2004 23:18, Larry Hall wrote:
> At 10:13 PM 6/3/2004, you 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.
> > Thanks.
> >David
> >
> >debug1: userauth-request for user dcorbin service ssh-connection method
> > publickey debug1: attempt 1 failures 1
> >debug2: input_userauth_request: try method publickey
> >debug1: test whether pkalg/pkblob are acceptable
> >debug3: mm_key_allowed entering
> >debug3: mm_request_send entering: type 20
> >debug3: monitor_read: checking request 20
> >debug3: mm_answer_keyallowed entering
> >debug3: mm_answer_keyallowed: key_from_blob: 0x100ecb30
> >debug1: temporarily_use_uid: 11141/10513 (e=18/544)
> >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys
> >debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED
> >debug3: mm_request_receive_expect entering: type 21
> >debug3: mm_request_receive entering
> >debug1: restore_uid: (unprivileged)
> >debug1: temporarily_use_uid: 11141/10513 (e=18/544)
> >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys2
> >debug1: restore_uid: (unprivileged)
> >debug3: mm_answer_keyallowed: key 0x100ecb30 is disallowed
> >debug3: mm_request_send entering: type 21
> >debug2: userauth_pubkey: authenticated 0 pkalg ssh-dss
> >Failed publickey for dcorbin from 172.16.5.102 port 1697 ssh2
>
> I can't tell from this.  Yours and my output diverge after the line in
>
> your file reading:
> >debug1: trying public key file /home/dcorbin/.ssh/authorized_keys
>
> Mine goes on with:
>
> debug3: secure_filename: checking '/users/lhall/.ssh'
> debug3: secure_filename: checking '/users/lhall'
> debug3: secure_filename: terminating check at '/users/lhall'
>
> Given that yours is "waiting", my WAG is that your home is not local.
> Things may also be complicated by the fact that your user is a domain
> user.  That's pretty tenuous but I don't have access to a domain
> environment at the moment so I can't try it for myself.  You might
> want to try logging in as a local user though.  But if you're home
> directory is a UNC share that requires password authentication, that's
> going to be your real problem.  Otherwise, you must have some permissions
> problem.  Your best bet is to grab the source and track where the "waiting"
> message is that you get.  That should help provide some context.
>

Thanks.  My home directory is NOT a UNC share, though the user is a domain 
user as your surmised (somehow).   I'll give your suggestions a try.
>
>
>
>
> --
> Larry Hall                              http://www.rfk.com
> RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> 838 Washington Street                   (508) 893-9889 - FAX
> Holliston, MA 01746

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