>From elsewhere comes the reminder that we're (a) merging our password
and shadow maps from the server (probably not a big deal) and (b) using
MD5 hashes for our passwords (probably a big deal).
So, given that we have an existing network of about twenty Red Hat boxes
that would like to continue to support their users, is there any way to
fold our new Solaris box into the net without monstrous upset for
everybody else?
"Michael R. Jinks" wrote:
>
> Greetings. This should really be posted to a Solaris support venue,
> but, well... anyhow.
>
> We have an NIS domain hosted on a Red Hat 7 box. Works great.
> Authenticates about twenty workstations, which up to now have also been
> Red Hat boxen.
>
> Had to set up a Solaris 8/intel box today. Mostly works fine. Binds to
> the NIS domain, mounts NFS volumes, looks good.
>
> BUT, whenever anybody tries to authenticate via NIS, it rejects their
> password. "su - <username>" from root works fine. ypcat produces maps
> as it's supposed to. UID's all resolve properly in file listings. But
> password authentication barfs.
>
> Anybody know what's going on here? Do I need to put magic symbos in
> /etc/passwd? (Shouldn't that be a thing of the past by now, or is it
> still necessary in non-Linux environments?)
>
> Alternately, anybody got a magic pill that will get all our clients off
> Slow Larry and onto Linux or *BSD by, say, 9am CST tomorrow?
>
> --
> Michael Jinks, IB // Technical Entity // Saecos Corporation
> Opinions expressed above are my own, and not those of my employer.
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
--
Michael Jinks, IB // Technical Entity // Saecos Corporation
Opinions expressed above are my own, and not those of my employer.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
