Date: Tue, 20 Aug 2002 15:34:06 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Byron Schlemmer <me@byron.me.uk> Cc: FreeBSD-Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Strange SSH publickey behaviour Message-ID: <20020820143406.GC16482@happy-idiot-talk.infracaninophi> In-Reply-To: <20020820150143.J2629-100000@pan.ehsbrann.com> References: <20020820133729.GD16083@happy-idiot-talk.infracaninophi> <20020820150143.J2629-100000@pan.ehsbrann.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 20, 2002 at 03:11:58PM +0100, Byron Schlemmer wrote:
> Thanks Matthew but none of the above apply. :) By this I mean my .ssh
> dir is 700 and the authorized_keys2 is set to 600. And as far as I know
> that is correct? User and group is set to me. Still looking around.
> It's driving me nuts.
Hmmm... A good trick to use is to run sshd on an alternate port on the
troublesome machine, with the depug level turned way up: sshd is
usually more forthcoming about exactly why an authentication method
was rejected than you can get out of the ssh side:
As root, on the troublesome machine:
sshd -d -d -d -p 2222
=46rom your usual system:
ssh -v -v -v -p 2222 troublesome
(Port 2222 is just an arbitrary choice. Substitute whatever is more
convenient if you need to.) The sshd process will print loads of
debug output and exit at the end of your ssh session. Should provide
a few clues.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Tel: +44 1628 476614 Marlow
Fax: +44 0870 0522645 Bucks., SL7 1TH UK
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020820143406.GC16482>