Date: Wed, 23 May 2001 13:00:41 -0400 (EDT) From: David Miller <dmiller@sparks.net> To: Jano Lukac <jedovaty@yahoo.com> Cc: freebsd-stable@freebsd.org Subject: Re: 4.3R and ssh problems Message-ID: <Pine.BSF.4.21.0105231256330.50961-100000@search.sparks.net> In-Reply-To: <20010522211931.86681.qmail@web14501.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 May 2001, Jano Lukac wrote: > > --- David Miller <dmiller@sparks.net> wrote: > > > chmod 4555 /usr/bin/ssh let it work too, so now I'm OK. Hopefully anyone > > else who runs into the problem will search the stable archive, but I > > always worry when defaults change. > > Wouldn't it be better to simply use the public/private keying system > (sshkeygen), and setup the keys without a password? I tested that and may well do it. The issue was that something which used to work, and is documented in the manpage as working does not, in fact work. This changed behavior will break existing scripts of people using .shosts and scp to copy web logs, for example. The auth log used to give a warning about what was going on, but now just says it's invoking PAM with nary a clue about why passwords are now required to be typed in. The man page should be changed too, to either mention the problem or to remove the references to authentication by .shosts files. --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0105231256330.50961-100000>