> doesn't have to be the same username..
>
> if it's the same username you can use hosts.equiv and bypass the ssh key
>
> -Justin
Yeah, but if you bypass the ssh key, you'll have an insecure connection. It's
better to use .rhosts or .shosts and an RSA key with no passphrase. That way
you can login with no password and it'll be secure. That's not the issue
anyway. The issue is thy guy had an old password in his key. If he wants to
bypass it, that's fine, but most people use ssh for the encryption.
-John Scott
On Thu, 08 Jul 1999, you wrote:
> >
> > Have you tried using ssh-keygen to generate a new public key for the problematic
> > user? The old password you are talking about is probably a passphrase embedded
> > in the public key for the user. Use ssh-keygen to generate a new key and copy
> > ".ssh/identity.pub" on machine 1 to .ssh/authorized_keys on machine 2.
> > Furthermore, If the user on machine 1 is the same username on machine 2, you
> > can generate a public key without entering a passphrase, allowing you to
> > connect via ssh without a password.
>
> doesn't have to be the same username..
>
> if it's the same username you can use hosts.equiv and bypass the ssh key
>
> -Justin
>
> |--------------------------------------------------
> | Justin Ryan
> | Developer Relations Associate
> | TurboLinux - http://www.turbolinnux.com/
> | [EMAIL PROTECTED]
> | WebMaster, PCHelp - http://computers.iwz.com
> | [EMAIL PROTECTED]
> |--------------------------------------------------
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
