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 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/sbin/sshd began to refuse
> > supporting protocol 1 with identical message
> > (`no RSA support in libssl and libcrypto. See ssl(8)'). Also,
> > kernel was build with `device random', and
> >
> > netch@iv:/usr/HEAD/src/sys/i386/conf>egrep '(RSA|USA)' /etc/make.conf
> > # If you're resident in the USA, this will help various ports to determine
> > USA_RESIDENT= NO
> > WITH_RSA=YES
> You missed (and deleted) the bit where it tells you to rerun MAKEDEV
> to rebuild your devices.
No, /dev/urandom was correct, 'MAKEDEV all' was run properly.
The only change was to remove old libraries, which are not installed
via installworld in modern -CURRENT, from /usr/lib.
> > And, my questions are
> > 1) What can happen to refuse RSA support in libcrypto, with environment
> > described above?
> An incorrect /dev/urandom
No.
> > 3) Can anybody provide more descriptive message when random device
> > works improperly?
> Yes. I'm working on making the random device itself moan at you.
Thank you for polite reply.;) But, the problem is not solved in this way.
That's why I asked some description how to diagnose these problems.
Instead of its I received random moans. Ok, thanks.
/netch
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
