OpenSSH and keys

[mikebw at colossus.bilow.com (Mike Bilow)]

I gave up on TeraTerm because it was just too flaky.  In particular, I
found that I liked Putty a great deal better, and it has Pscp (an scp
port) available:

	http://www.chiark.greenend.org.uk/~sgtatham/putty.html

A common problem with upgrading SSH is that protocols may be disabled for
legal reasons, especially RSA or IDEA.  The default for most free SSH
implementations is to use 3DES instead of IDEA, for example.

See if your client has some sort of "verbose" mode for reporting
connection progress in detail.

-- Mike


On 2000-07-07 at 21:13 -0400, Subba Rao wrote:

> Hello
> 
> I was using openssh-1.2.1 for a while and recently switched to
> openssh-2.1.1
> 
> With the older version of openssh, I could establish connection to my
> server over the Internet. With the newer version, the keys that are
> generated by ssh-keygen do not allow me to connect to my server. The server
> accepts the keys generated by the older version of ssh.
> 
> My ssh client is TeraTerm Pro for windows. I do not think that should make
> any difference. This client works fine with the old keys and the new server.
> I do not why the new keys are not working with the new server.
> 
> Is anyone else experiencing this problem?


-
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).