From owner-freebsd-current Mon May 7 9:18: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 57ACB37B423 for ; Mon, 7 May 2001 09:18:01 -0700 (PDT) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (grolsch.ai [209.88.68.214]) by cypherpunks.ai (Postfix) with ESMTP id BAD3049; Mon, 7 May 2001 12:17:52 -0400 (AST) Message-ID: <3AF6CAB0.D7C8C5BE@vangelderen.org> Date: Mon, 07 May 2001 12:17:52 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: ssh reports "no RSA support in libssl and libcrypto." References: <20010507091631.H59150@gsmx07.alcatel.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > Having built and installed -current from last Friday, I find that ssh* > is now reporting "no RSA support in libssl and libcrypto. See ssl(8)" > and will only talk SSH2. I couldn't find anything relevant in ssl(8). > > I haven't specified "WITH_RSA=NO" anywhere and checking through the > build logs, there's no sign of "-DNO_RSA". libcrypto.a contains an > RSA_generate_key() which doesn't look like a stub. > > Does anyone have any ideas? I seem to remember that I once got a misleading message just like that. It turned out that /dev/random was not available or not working properly. Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org "A government that robs Peter to pay Paul can always depend upon the support of Paul." -- George Bernard Shaw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message