Date: Thu, 26 Feb 2004 02:09:10 -0500 From: "Mike Jakubik" <mikej@rogers.com> To: "'John Hay'" <jhay@icomtek.csir.co.za>, <current@freebsd.org> Subject: RE: sshd_config 1.35 commit Message-ID: <20040226070814.VNVO83660.fep01-mail.bloor.is.net.cable.rogers.com@win2000> In-Reply-To: <20040226070242.GA72677@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-current@freebsd.org > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of John Hay > Sent: Thursday, February 26, 2004 2:03 AM > To: current@freebsd.org > Cc: Mike Jakubik > Subject: Re: sshd_config 1.35 commit > > On Thu, Feb 26, 2004 at 08:24:25AM +0200, John Hay wrote: > > > > > > I have built world recently, only to find out I cant > log into my > > > server via ssh anymore. Am I the only one that thinks disabling > > > password authentication in default sshd is a stupid idea? I think > > > this is a pain in the ass, like the 'no root login' option wasn't > > > enough. A nice heads up or entry in UPDATING would have > been nice, > > > so people don't get locked out after updating. > > > > I agree with you, it has bitten me already too. :-((( My > vote would be > > for backing it out. > > Replying to myself, maybe it isn't so bad and an entry to > UPDATING might be enough. In my case I had to add an > > PreferredAuthentications publickey,password > > entry to .ssh/config a while back because otherwise I > couldn't log in to some older machines. It looks like adding > keyboard-interactive at the end of that line fix my problems. > SecureCRT seems to work with authentication type: interactive-password, however only after the second try. In my opinion this is a major PITA. I have no time to memorize all my logins, or type them in.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040226070814.VNVO83660.fep01-mail.bloor.is.net.cable.rogers.com>