> >
> > Ssh-keygen2 will create ~/.ssh2 and a pub/priv keypair.
> > Transport the private key to the remote host
>
> The _private_ key? That kind of defeats its purpose.
>
Um, this is the wrong way around.
> > On the remote host:
> > create ~/.ssh2
> > save the public key in a file: hostname.pub
> > echo "Key hostname.pub" >> authorization
> >
> > If it were not for the unkind license, I would recommend using ssh2 at
> > all times. The license however...
>
> OpenSSH does 2.0, or so they claim. What are the improvements between 1
> and 2?
>
OpenSSH 2 does support both SSH1 and SSH2 protocols, some way they worked
around the licensing problem (I don't know the details), but it's
distributed with BSD license.
SSH2 has better handshaking and key exchange, it's also more optimized in
file transfers and especially tunneling.
I use SSH2 whenever I can, I however can receive a number of copies I
like for free as long as I work here (F-Secure corp). Actually I could
have a short talk with our sales/marketing dept, The Greywolves got their
server license and a bunch of clients this way.
/Rambo
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
