Sat, May 12, 2001 at 04:24:29, tlambert2 (Terry Lambert) wrote about "SSH Must Die":
> This whole ssh B.S. is very annoying.
> After an upgrade from 4.2 to 4.3 using a CDROM boot plus
> upgrade menu option, SSH stops working, for no good reason
> (_any_ reason is no good).
> It complains about RSA not being in libcrypto, even though
> "nm" shows that that claim is full of crap.
> Yes, I have /dev/random, and yes, I have it in my kernel,
> even though it makes my boots slow as hell.
Oh. The random device which needs entropy seed is -current artifact,
isn't it?
On -current, I watched identical problem with mystical ssh brokenness,
with "No RSA support in libcrypto and libssl" message from ssh,
after when all possible underwater stones were verified (including
/dev/random and /dev/urandom, respect to markm@ reply). Unfortunately
I had to make this system working in any way before I could do any
diagnose, and it was completely rebuilt to RELENG_4. But, your case
seems to be another.
> How do I update the whole thing, so that the problem goes
> away?
> Alternately, can we rip it bodily out of FreeBSD, and
> flush it down the toilet?
Do you know another SSH implementation with good license?
/netch
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
