On Tue, 29 Aug 2000, Jonathan Wilson wrote:
> Ok,
>
> 1. I did need to re-run the keygens, both ssh-keygen and ssh-keygen2
>
> It appears that this new rpm I have has all the stuff for both ssh and
> ssh2, and ssh2 is what's running by default.
> If I telnet the "garnet" (the Red Hat box in question) I can then do "ssh2
> 192.168.0.80" and connect.
> If I use ssh, I cannot connect.
> Apparently that's why putty and SuSE are failing - they have the original
> Ssh, I guess.
> Time to upgrade :-)
>
> In ps -auxw I now see sshd2, but not sshd.
>
> I can live with this, but don't you think it should fall back to ssh 1? The
> way I got it running was to enable it as a service in "setup" and there's
> only one option.
> Can I have them both running, or is there something I can edit that would
> cause it to default to ssh1 when the client isn't ssh2 compatible?
>
> JW
>
Not sure. I only know that ssh2 caused a lot of problems whenever clients
used the older version of ssh, and that's why I suggested to take a look
into that. Personally, I choose to run either OpenSSH or ssh-1.2.27/29
(there have been several upgrades due to security holes), although I admit
I had to do it due to license restrictions that do not apply anymore. I
must say I never experienced any problem with those other versions though.
-------------------------------
Nitebirdz
http://www.linuxnovice.org
Your place for tips, news, etc.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
