Re: Getting ssh back to work?
On Sat, 23 Sep 2000, Mark Huizer wrote: > I thought I had read the interesting stuff on ssh recently in -current, > but I can't get ssh to work again on the machine I switched to > yesterday's current :-( device random in your kernel. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Getting ssh back to work?
Hello! On Sat, Sep 23, 2000 at 02:01:21PM +0200, Mark Huizer wrote: > tiggr 1:31pm [~/.ssh] ssh eeyore > ssh: no RSA support in libssl and libcrypto. See ssl(8). > Disabling protocol version 1 > DH_generate_key > > That's with USA_RESIDENT=NO, and with rsaref port installed. ?? Can you give me a reason for doing this?:-) Rsaref (was) only for USA_RESIDENT=yes. If you are using a recent -CURRENT, crypto stuff is no longer separate, but comes with the base system. So you can basically just install the CRYPTO collection (and sources if you like) in sysinstall, or do a 'make world' with full sources. (a cvsup beforehand will take care of this.) Hope this helps... -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Getting ssh back to work?
Hmm... I thought I had read the interesting stuff on ssh recently in -current, but I can't get ssh to work again on the machine I switched to yesterday's current :-( tiggr 1:31pm [~/.ssh] ssh eeyore ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 DH_generate_key That's with USA_RESIDENT=NO, and with rsaref port installed. doing a ssh-keygen -d will just give me: tiggr 1:32pm [~/.ssh] ssh-keygen -d Generating DSA parameter and key. DSA_generate_keys failed That helps :-( Is there anything I've forgotten to do to make it work? mark -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
