From owner-freebsd-current Fri Mar 30 15:54:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id F0B6037B71D for ; Fri, 30 Mar 2001 15:54:41 -0800 (PST) (envelope-from tmoestl@gmx.net) Received: (qmail 4469 invoked by uid 0); 30 Mar 2001 23:54:40 -0000 Received: from p3e9bc0a5.dip.t-dialin.net (HELO forge.local) (62.155.192.165) by mail.gmx.net (mp004-rz3) with SMTP; 30 Mar 2001 23:54:40 -0000 Received: from tmm by forge.local with local (Exim 3.20 #1) id 14j8j0-0001NJ-00; Sat, 31 Mar 2001 01:54:38 +0200 Date: Sat, 31 Mar 2001 01:54:37 +0200 From: Thomas Moestl To: The Hermit Hacker Cc: freebsd-current@freebsd.org Subject: Re: ssh: no RSA support in libssl and libcrypto. See ssl(8). Message-ID: <20010331015437.A5130@crow.dom2ip.de> Mail-Followup-To: Thomas Moestl , The Hermit Hacker , freebsd-current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from scrappy@hub.org on Fri, Mar 30, 2001 at 06:36:51PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 30, 2001 at 06:36:51PM -0400, The Hermit Hacker wrote: > > how does one fix this? *puzzled look* there is no ssl(8) that I can seem > to find to See, and nothing apparent in the UPGRADING file ... system > uptodate as of last night, and mergemaster just finished completing ... > > ssh: no RSA support in libssl and libcrypto. See ssl(8). > Disabling protocol version 1 > DH_generate_key Do you have device random in your kernel configuration? Absence of a working random device triggers this bug. The need for this is also documented in UPDATING. - thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message