Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!nosc!crash!jadpc!jdeitch
From: jdeitch@jadpc.cts.com (Jim Deitch)
Newsgroups: comp.unix.sysv386
Subject: Re: Needed: pcnfsd that knows about /etc/shadow
Keywords: a fix is enclosed....
Message-ID: <1991Feb26.155310.1278@jadpc.cts.com>
Date: 26 Feb 91 15:53:10 GMT
References: <9004@sail.LABS.TEK.COM> <1991Feb22.035906.11349@buster.stafford.tx.us> <15478@uudell.dell.com>
Distribution: na
Organization: Network Engineering Technologies, San Diego, CA.
Lines: 33

In article <15478@uudell.dell.com> sblair@upurbmw.dell.com (Steve Blair) writes:
>[a customer emailed this fix to us, thought it'd share it]
>
>Here's a quick and simple way to avert any problems with pcnfsd.c A message
>from someone posted to comp.unix.sysv386 clued me in on what was going on.
>pcnfsd, as distributed by SUN, doesn't support shadow password files. It 
>uses getpwnam() to get the /etc/passwd entry for a particular user. Under your
>UNIX, the passwd structure returned does not include the encrypted password. 
>Because of this, it didn't have a password to compare against the one I was
>passing over from the PC NFS client and so it failed the mount every time. 
>To correct this, I added code to pcnfsd.c (source to which is distributed with
>SUN's PC-NFS and FTP Software's PC/TCP) to additionally call getspnam() to 
>access the shadow password file to retrieve the user's password. This was 
>a trivial modification. 
>
>
>
>
>-- 
>Steve Blair	DELL	UNIX	DIVISION sblair@upurbmw.dell.com
>================================================================

You will find this true of most of the bsd stuff.  I ported pop and
uucpd from BSD and had to do the mods.  Be advised that the structures
between passwd and shadow are a little different, along with the
routines that you have to use.

Jim

-- 
ARPANET:    jadpc!jdeitch@nosc.mil
INTERNET:   jdeitch@jadpc.cts.com
UUCP:	    nosc!jadpc!jdeitch