openssh unix dev - Oct 2001 - OpenSSH_2.9.9p2 Configuration problem

I've recently upgraded some of my machines from an ssh1 environment to
an openssh one, and consequently, I'm now using the ssh2 protocol.  I
can't seem to get it to allow remote logins without prompting for a
passphrase or password.  Is this possible?  I've created id_dsa and
id_rsa files etc., using ssh-keygen and have copied the public
information to the remote authorized_keys files from the other ends of
the connections.

When I try to connect, I get propted for the rsa passphrase, and if I
don't give it, the dsa one, and finally the password.

I prefer the ssh1 behavior, although, adding the information to the
various authorized_keys files is no great hardship.

Any suggestions?

I don't subscribe to this list, so please cc me directly.


David

David Ronis wrote:
> I've created id_dsa and
> id_rsa files etc., using ssh-keygen and have copied the public
> information to the remote authorized_keys files from the other ends of
> the connections.
That's your problem.  After you have created your passwordless key(s), 
you will want to add them to the remote authorized_keys2 file. 
  authorized_keys is only used for ssh1 connexions.

I found this out myself after much pain and error.

Hi Markus,

Thanks for the reply.  I had copied the public keys to authorized_keys
on the remote machine and the remote's to the local.  I did specify a
passphrase when creating the keys.  Is this the problem?

Also, is ssh2 really worth the effort?  I've disabled the traditional
rsh/rlogin/rcp programs on all my machines, so what else would ssh2
offer over ssh1?

David

You wrote:
> in 2.9.9 authorized_keys is used for both protocol versions.
> 
> On Wed, Oct 17, 2001 at 03:14:56PM -0700, vsync wrote:
> > 
> > 
> > David Ronis wrote:
> > > I've created id_dsa and
> > > id_rsa files etc., using ssh-keygen and have copied the public
> > > information to the remote authorized_keys files from the other
ends of
> > > the connections.
> > 
> > That's your problem.  After you have created your passwordless
key(s),
> > you will want to add them to the remote authorized_keys2 file. 
> >   authorized_keys is only used for ssh1 connexions.
> > 
> > I found this out myself after much pain and error.
> > 
>