Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!rpi!dali.cs.montana.edu!ogicse!pdxgate!parsely!percy!percival.rain.com!nerd
From: nerd@percival.rain.com (Michael Galassi)
Newsgroups: comp.sys.next
Subject: Re: getpwnam on the NeXT
Message-ID: <1991Jun17.144725.11762@percy.rain.com>
Date: 17 Jun 91 14:47:25 GMT
References: <3NG-_4-@engin.umich.edu> <1752@toaster.SFSU.EDU>
Sender: news@percy.rain.com (news maintainer)
Organization: Percy's UNIX, Portland, OR.
Lines: 17
Nntp-Posting-Host: percival.rain.com

eps@toaster.SFSU.EDU (Eric P. Scott) writes:

>You're confused.  getpwnam() on the NeXT knows about NetInfo and
>YP/NIS, and does "the right thing."  *DO NOT* attempt to read
>/etc/passwd directly nor use getpw()--stick with getpwnam() and
>getpwuid().  If you use setpwfile(), all bets are off.

I did some checking here, setpwfile(3) is ignored if you are doing
NetInfo, very much of a pain.  I needed this to read password files
off other machines on the network to do checking for 'obvious'
passwords.   The workaround was to convert password files to word
lists with vi <yuck>.

-m
-- 
Michael Galassi				| nerd@percival.rain.com
MS-DOS:  The ultimate PC virus.		| ...!tektronix!percy!nerd