Very Computer

Hi all,

I have a few solaris machines ranging from 2.5.1 to 7 that passwords
via NIS no longer work on.  The NIS master is a linux machine that had
just been upgraded a few weeks ago.  After the upgrade, passwords on
the solaris clients stopped working.  I can do anything and everything
NIS related between the solaris client and the linux master, except
for execute yppasswd or login.  This had been working fine when we
were previously running the NIS master on a RedHat 7.1 machine.

When I try to login to the solaris machine, it says the password is
invalid.  If I login as root and run 'yppasswd username', i get this:

bash-2.01# yppasswd jason
Enter login(NIS) password:
Sorry: wrong passwd
Permission denied

But the password is right.  I tried downgrading the NIS master last
night to see if that was the problem, but that made no difference at
all.  I'm assuming it has something to do with the password encryption
but have no clue where to look or what to do.

Can anyone please help me with this issue?  Let me know if you need
any additional information too.

Thanks,

JP

My guess is that RH machine is using MD5 encrypted passwords, which the
Solaris machines don't understand.  Configure your RH server to use
crypt-style encryption (or better: upgrade it to Solaris) and all should
be well.

Quote:> all.  I'm assuming it has something to do with the password encryption
> but have no clue where to look or what to do.

Probably; see above.

HTH,

--
Rich Teer, SCNA, SCSA

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: http://www.rite-online.net

I ended up figuring out that md5 was the problem.. I disabled md5 on
the linux box and it was still creating md5 password for some reason.
I didn't have much time to investigate this issue as it was something
that needed to be taken care of ASAP, so i applied a bandaid to the
wound until I can find time to operate.

Basically I generated a password on the solaris box and then copied
the encrypted password into the shadow file on the linux machine and
all was working fine for the users in question.

Thanks for the help,

JP