First Try at Creating Website

[David A. Bandel]

OK, time to understand what you're doing.  -t rsa creates an ssh2 rsa key.
 This is not standard.  Try this: ssh-keygen
let it save that to identity and identity.pub.  The identity.pub is copied
to the other system's authorized_keys file.  This command will give you an
ssh1 compatible authentication key.

For ssh2, try:
ssh-keygen -t dsa
let it save that to id_dsa and id_dsa.pub.  then id_dsa.pub is copied to
the other system to authorized_keys2 (not authorized_keys).  You can
substitute id_rsa.pub into authorized_keys2 if you want, but not all
systems will recognize this (and it's not as good as dsa).

Ciao,

David A. Bandel

On Thu, 21 Mar 2002 22:01:42 +0800
begin  "M.W.Chang" <linuxism at yahoo.com> spewed forth:

> did you use rsa key in your protocol 2?
> I generated the key using ssh-keygen -t rsa,
> copied the id_rsa.pub to authorized_keys, and move
> the id_rsa to putty. no luck.
> putty kept saying something like "no supported authenatication left to
> try"
> 
> Bill Day wrote:
> > 
> > I have putty on a winbox, and it has protocol 2.  Version 0.51  It
> > does default to protocol 1 unless you save the info.  It also offers
> > the following encryption:
> > 3DES, Blowfish and DES
> > None of which I really know the difference in, since I just use the
> > default of 3DES for it.
> 


-- 
Focus on the dream, not the competition.
		-- Nemesis Racing Team motto
Internet (H323) phone: 206.28.187.30