From owner-freebsd-hackers Sat May 12 6: 0: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.hutchtel.net (ns1.hutchtel.net [206.9.112.100]) by hub.freebsd.org (Postfix) with ESMTP id CE2E937B443 for ; Sat, 12 May 2001 06:00:01 -0700 (PDT) (envelope-from jpaetzel@hutchtel.net) Received: from mark9.vladsempire.net (hutch-228.hutchtel.net [206.10.67.156]) by ns1.hutchtel.net (8.9.1/8.9.0) with SMTP id HAA01753; Sat, 12 May 2001 07:59:58 -0500 (CDT) Content-Type: text/plain; charset="iso-8859-1" From: j To: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: SSH Must Die Date: Sat, 12 May 2001 08:05:36 -0500 X-Mailer: KMail [version 1.2] References: <3AFD1D6D.51731EAC@mindspring.com> In-Reply-To: <3AFD1D6D.51731EAC@mindspring.com> MIME-Version: 1.0 Message-Id: <01051208053600.00484@mark9.vladsempire.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday 12 May 2001 06:24, Terry Lambert wrote: > This whole ssh B.S. is very annoying. > > After an upgrade from 4.2 to 4.3 using a CDROM boot plus > upgrade menu option, SSH stops working, for no good reason > (_any_ reason is no good). > You did make the needed additions to /etc/pam.conf, didn't you? > It complains about RSA not being in libcrypto, even though > "nm" shows that that claim is full of crap. > > Yes, I have /dev/random, and yes, I have it in my kernel, > even though it makes my boots slow as hell. > > How do I update the whole thing, so that the problem goes > away? > > Alternately, can we rip it bodily out of FreeBSD, and > flush it down the toilet? > > -- Terry What would we use for remote command line access if that happened? Josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message