ssh setup

[jcallen at narsil.com (Jerry Callen)]

"Brian J. Conway" wrote:

> The bottom line is that ssh1 and ssh2 are using completely different ssh
> protocols and clients and servers must match.  Due to the commercialized
> nature of ssh2, the majority of the open-source community considers ssh1
> to be the standard.  I'd stick with that.

Note, however, that ssh2 does have hooks in the server to allow it to forward a
connection to an ssh1 server if an ssh1 client attempts to connect to the ssh2
server. I run this on my own system and it works fine. Since at least some
copmmercial ssh2 clients are *not* backward compatible to ssh1 (a nasty
marketing
ploy, I suspect...), this is a handy feature if you have to support both ssh2
and ssh1 clients.


-- Jerry Callen                      Mobile: 617-388-3990
   Narsil                            FAX:    617-876-5331
   63 Orchard Street                 email:  jcallen at narsil.com
   Cambridge, MA 02140-1328

   PGP public keys available from http://pgp.ai.mit.edu
   fingerprints:
       DH/DSS key ID 0x1806252C: 7669 A4CD 759A 6EB7 AF04
                                 C10D B659 2A4B 1806 252C
       RSA    key ID 0x99F7AAE5: D265 DC9C 13FD 6110 
                                 30F5 1874 A206 24B1
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).