Date: Mon, 4 Oct 1999 16:05:21 -0400 From: "Troy Settle" <st@i-plus.net> To: "FreeBSD ISP" <freebsd-isp@freebsd.org> Subject: RE: One password base for some *NIX boxes Message-ID: <NDBBKPEMLJEBDEPFNHOHKEEPCAAA.st@i-plus.net> In-Reply-To: <199910041921.MAA70531@pau-amma.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >The easiest answer, is NIS. But, NIS isn't exactly secure. > > True enough. > > >... > > >When implementing this, you'll need to educate your users so > they'll know to > >change their passwords on the master server only .... > > It's not apparent to me why the above suggestion was made. > > Within the Engineering net here, we use NIS. And I assure you that my > desktop isn't even a NIS slave server. You missed the 2nd paragraph of my post... I'd already left NIS out of the picture as a solution: >> I'd reccomend that you select one box to be your master server, >> then use ssh and some perl to generate and distribute appropriate >> passwd and shadow files to the other servers. > > Yet: > > pau-amma[1]% passwd > Changing NIS password for dhw on prawn.whistle.com. > Old Password: > > you will see that I had an opportunity to change my NIS password from a > NIS client machine, using the usual "passwd" command. Of course, but again, I stopped talking about NIS after the first line of my post. Laterz, Troy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBKPEMLJEBDEPFNHOHKEEPCAAA.st>