On Mon, Oct 08, 2001 at 09:11:09AM -0700, Bob Miller wrote: > Rob Hudson wrote: > > > Recently, in debian woody, openssh 2.9p2 came thru and was set to use > > ssh2 by default. I used to have a key on my server so I could just > > ssh to it without having to log in. With ssh2, there is no ssh2 key > > over on the server. > > > > Can I mix keys in .ssh/authorized_keys? Or do I create a > > .ssh/authorized_keys2? > > Run ssh-keygen -t <other args>. "-t" is for two, I guess. > actually, -t is for type; type being rsa1, rsa or dsa rsa1 is used for SSH1, the others for SSH2. The default is RSA1, so the "-t" is for two is an easy way to remember.
> ssh-keygen creates .ssh/authorized_keys2. > No. ssh-keygen creates identity[.pub], id_rsa[.pub], id_dsa[.pub] There are some scripts to add keys to authorized_keys files on remote systems after the first password login, but I don't remember the names or where they come from. You should use authorized_keys2 for SSH2, and authorized_keys for SSH1. > The ssh-keygen man page describes this better than I could. > They're pretty thorough, that's for sure :) -- <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
