[lug] problems with ssh key authorization after

[dan radom]

Hugh,

ssh2 uses dsa keys.  ssh-keygen -t dsa

dan

* Hugh Brown (hugh at vecna.com) wrote:
> I seem to remember that ssh1 was fundamentally flawed and allowed for a
> theoretical hack even though the hack would be really hard to implement.
> 
> Does anyone know how to generate an ssh2 style RSA key?
> 
> Hugh
> 
> "dan radom"
> > 
> > I've found that ssh2 is much faster for port forwarding.  I don't really use ssh1 anymore, so I'm not sure about the speed of that protocol.  It should like you've got a client (ssh) configured to use ssh1 and a daemon (sshd) configured to use ssh2.  Configure them both to use the same protocol and generate the appropriate keys and you shouldn't have to specify -1 or -2 anymore.
> > 
> > dan
> > 
> > > 	i havent tried switching the 2,1 to 1,2 or anything else within
> > > 	the ssh/sshd config files, however i was able to get rsync up
> > > 	and running properly (meaning that no passwords were prompted)
> > > 	by using
> > > 
> > > 	  rsync -e "ssh -1"
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug