From owner-freebsd-current Mon Mar 19 3: 9:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 8809C37B719 for ; Mon, 19 Mar 2001 03:09:38 -0800 (PST) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (Postfix) with ESMTP id 3B0FC1C8DD; Mon, 19 Mar 2001 12:09:37 +0100 (MET) Received: by bofh.enst.fr (Postfix, from userid 12426) id 09115D26E; Mon, 19 Mar 2001 12:09:32 +0100 (CET) Message-ID: <20010319120932.A88999@enst.fr> Date: Mon, 19 Mar 2001 12:09:32 +0100 From: Pierre Beyssac To: freebsd-current@freebsd.org Subject: random woes ("no RSA support in libssl and libcrypto") Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just in case some else gets caught (which is sure to happen), in case you get the following obscure message from ssh after updating your -current: ssh: no RSA support in libssl and libcrypto. See ssl(8). This just means you need to remake your /dev/urandom (ln -f random urandom). It seems the compatibility with the previous minor of urandom has been silently removed (I assume this happened with the last update/cleanup of the random device). It took me two hours to figure it out. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message