From owner-freebsd-current@FreeBSD.ORG Wed Feb 25 23:08:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CAB816A4CE for ; Wed, 25 Feb 2004 23:08:42 -0800 (PST) Received: from fep01-mail.bloor.is.net.cable.rogers.com (fep01-mail.bloor.is.net.cable.rogers.com [66.185.86.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id C436A43D1F for ; Wed, 25 Feb 2004 23:08:41 -0800 (PST) (envelope-from mikej@rogers.com) Received: from win2000 ([63.139.3.63]) by fep01-mail.bloor.is.net.cable.rogers.comESMTP <20040226070814.VNVO83660.fep01-mail.bloor.is.net.cable.rogers.com@win2000>; Thu, 26 Feb 2004 02:08:14 -0500 From: "Mike Jakubik" To: "'John Hay'" , Date: Thu, 26 Feb 2004 02:09:10 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <20040226070242.GA72677@zibbi.icomtek.csir.co.za> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 thread-index: AcP8No/y1vK4QOoeTEyLYSddpLli3gAAJO3g X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep01-mail.bloor.is.net.cable.rogers.com from [63.139.3.63] using ID at Thu, 26 Feb 2004 02:08:14 -0500 Message-Id: <20040226070814.VNVO83660.fep01-mail.bloor.is.net.cable.rogers.com@win2000> Subject: RE: sshd_config 1.35 commit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2004 07:08:42 -0000 > -----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.