it is very nice of you to try to help me, but i'm afraid i'm not the right
addressee. so i forwarded your reply to the list.
clemens
> Bigley, Stephen W.:
> Had this problem myself when I went from SSH1 to SSH2 recently. The problem
> exhibited itself on more than just Solaris. Running debug from the client
> showed what was happening (ssh -v -v -v). It will show the remote side
> looking for your local id_rsa.pub or id_dsa.pub. Turns out I had to put new
> keys into the remote ~/.ssh/authorized_keys2 for this to work. Also, on the
> local (client) side, had to gen a new key using ssh-keygen with the '-t rsa'
> (or '-t dsa' if you prefer) flag. ssh-keygen was creating an rsa1 key by
> default which broke my scripts. Using the -t flag, ssh-keygen then creates
> a ~/.ssh/id_rsa and id_rsa.pub file. Put the new local id_rsa.pub in the
> remote authorized_keys2 file, not the local identity.pub file.
>
>
> -----Original Message-----
> From: clemensF [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 26, 2001 3:31 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Hostbased Authentication and PAM with OpenSSH on Solaris
>
>
> > Dominique Frise:
>
> > We are using OpenSSH-2.9p1 on Solaris 8 with PAM enabled.
> > We are not able to use the HostbasedAuthentication: the server still ask
> > for a password.
> >
> > debug1: userauth-request for user root service ssh-connection method
> > none
>
> this is propably it. root is always treated specially. you might get what
> you want, but not with uid 0.
>
> clemens
