Tue, Mar 27, 2001 at 11:33:11, mark (Mark Murray) wrote about "Re: random woes ("no
RSA support in libssl and libcrypto")":
> > Well, but it says about `options RANDOMDEV'. Later, `device random' was
> > invented instead of it. A few days ago I instal
> > See src/UPDATING 2624
>
> Well, but it says about `options RANDOMDEV'. Later, `device random' was
> invented instead of it. A few days ago I installed -CURRENT
> (date=2001.03.25.12.00.00) with removing all previous content of /usr/lib
> (which contained legacy since 3.1-RELEASE) and /usr
On Tue, 27 Mar 2001, Valentin Nechayev wrote:
> And, my questions are
> 1) What can happen to refuse RSA support in libcrypto, with environment
> described above?
I suspect you need to remake /dev/urandom. Copy /usr/src/etc/MAKEDEV from
-current into /etc and remake the device. /dev/urandom is n
Mon, Mar 19, 2001 at 16:02:08, mark (Mark Murray) wrote about "Re: random woes ("no
RSA support in libssl and libcrypto")":
> > ssh: no RSA support in libssl and libcrypto. See ssl(8)
[...]
> > It seems the compatibility with the previous minor of 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.
See src/UPDATING 2624
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Uns
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
