home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.admin
- Path: sparky!uunet!utcsri!torn!newshub.ccs.yorku.ca!yorku.ca!davecb
- From: davecb@nexus.yorku.ca (David Collier-Brown)
- Subject: Re: Using rdist instead of NIS/YP?
- Message-ID: <davecb.724470371@yorku.ca>
- Sender: news@newshub.ccs.yorku.ca (USENET News System)
- Organization: York University
- References: <1992Dec11.211922.12767@alf.cooper.edu> <111326@siemens.siemens.com>
- Date: Wed, 16 Dec 1992 01:46:11 GMT
- Lines: 26
-
- Mr X asks:
- |>Anyone out there using rdist instead of NIS/YP for passwd serving?
-
- aad@siemens.com. (Anthony Datri) writes:
- |I've done it with passwd, aliases, and hosts, and I recommend it highly. You
- |avoid the usual YP hassles, especially the line-length limitations. [...]
- |The only potential problem is that the users need to get into the habit of
- |changing their passwords on the machine from which you rdist.
-
- You can also cross-mount password files (ie, leave a symlink in /etc
- pointing to a passwd file on a shared partition).
-
- To make any remote passwd scheme allow distributed updaters, we used
- a script for /etc/passwd that conected to a distinguished account on
- the master passwd server via rsh, passing the username as $TERM (:-)).
- The account's shell was a moronic password-changer.
-
- This is reproducable dozens of ways: I still have a copy of an ancient
- version which used ``on'' and was written in csh (:-().
-
- --dave (on is a security hole) c-b
- --
- David Collier-Brown, | davecb@CCS.YorkU.CA | lethe!dave
- 72 Abitibi Ave., |
- Willowdale, Ontario, | York Postmaster and
- CANADA. 416-223-8968 | occasional sendfail(8) consultant.
-