> from machine A (server), the correct users can telnet in to machine B(also has
> the outside world connection), ftp, sudo, and su work fine.
> But when I try to ssh in to machine 2, it only uses a passwd that I had in the
> old passwd file on machine 1.

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.

Also, make sure to chmod your .ssh directory in the user's folder on machine 2
to 700.  Chmod the .ssh/authorized_keys file to 600.  (and of course, make sure
the appropriate user owns the files.  That may eliminate additional problems.

--
John Scott
Residential Systems Administrator
KNOLOGY Holdings, Inc.

On Wed, 07 Jul 1999, you wrote:
> I recently set up a 2 system network at home, using RH 6.0 on both boxes.
> On one, (one on non localnetwork), I run NFS automount, and NIS server.
> I removed all users from the passwd file, and pointed the NIS maps at a
> separate location.
> from machine A (server), the correct users can telnet in to machine B(also has
> the outside world connection), ftp, sudo, and su work fine.
> But when I try to ssh in to machine 2, it only uses a passwd that I had in the
> old passwd file on machine 1.
> There is no copy of this passwd file.  I removed shadow, turned off all
> shadow/md5 authentication in the pam modules, and still nothing.
> the odd part, is that the users can ssh into the server using their new nis
> passwds.
> Also, rpc.yppasswd wont accept more than one connection, and then it goes to a
> stale state, still running but not communicating.
> If anyone has any info on this, I would be most appreciative.
> Thanks
> lasher
> ---------------------------------------------------------------------------
> Send administrative requests to [EMAIL PROTECTED]

---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]

Reply via email to