shadow files getting wiped out (standard passwd/shadow)

shadow files getting wiped out (standard passwd/shadow)

Post by Tobias J. Krei » Sat, 27 Jan 1996 04:00:00



We run a SPARCserver 1000, 256 MB memory, 4 CPUs, Solaris 2.4, with
over 11,000 accounts at Northern Arizona University.  We have been using
the standard passwd/shadow file systems for dealing with passwords,
partly because of security concerns with NIS/NIS+, plus NIS doesn't have
a particularly easy way to reset passwords if the user has forgotten
his/her password (and that happens a lot here).  We have had bad experiences
with conflicts in running the passwd utility to change passwords; due to
what we have concluded are an insufficiently robust dile locking mechanism in
passwd (it just "touches" /etc/.pwd.lock) we have had several times a day for
the last few days had our shadow file completely disappear!  This chaotic
condition is claimed to be probably due to a run condition by Sun, but
Sun says nobody else has this problem, so istead of fixing it, they
recommended we switch to NIS or NIS+.  So, my question is, given our
university environment, how have other similar institues dealt with managing,
and changing passwords on large machines like this?  What security concerns
have been addressed?  How do you deal with forgotten passwords?  Is kerberos
potentially a better solution?  Feedback would be most appreciated.

-- Tobias

+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+

 Computing Technology Services                //\   .  ,     Tel: 520-523-6158
 Northern Arizona University                //   `\//\//\    Fax: 520-523-7407
 Box 5100 (Bldg. 54A, Knowles Drive)      //       `  `  `\
 Flagstaff, AZ 86011                  ---''      N.A.U.    `---

 
 
 

shadow files getting wiped out (standard passwd/shadow)

Post by ron na » Mon, 29 Jan 1996 04:00:00


I suspect your using vipw which is broken under Solaris 2.4/2.5.  There
is a patch for Solaris 2.5.  Solaris 2.x locks the passwd/shadow file
by using lckpwdf() to set a kernel file lock on /etc/.pwd.lock.  This
is not a simple test to see if /etc/.pwd.lock exists.

We have been using our own ported version of npasswd and chfn/chsh
under Solaris 2.4 for over a year, and under Solaris 2.5 without
any loss of accounts in /etc/passwd or /etc/shadow.  A year ago
we had 8,000 accounts on Solaris 2.4, and current have 12,000 accounts
on our SS1000 running Solaris 2.5.  We do not use NIS/NIS+.


: We run a SPARCserver 1000, 256 MB memory, 4 CPUs, Solaris 2.4, with
: over 11,000 accounts at Northern Arizona University.  We have been using
: the standard passwd/shadow file systems for dealing with passwords,
: partly because of security concerns with NIS/NIS+, plus NIS doesn't have
: a particularly easy way to reset passwords if the user has forgotten
: his/her password (and that happens a lot here).  We have had bad experiences
: with conflicts in running the passwd utility to change passwords; due to
: what we have concluded are an insufficiently robust dile locking mechanism in
: passwd (it just "touches" /etc/.pwd.lock) we have had several times a day for
: the last few days had our shadow file completely disappear!  This chaotic
: condition is claimed to be probably due to a run condition by Sun, but
: Sun says nobody else has this problem, so istead of fixing it, they
: recommended we switch to NIS or NIS+.  So, my question is, given our
--

  ,;( )__, )~\|  |
 ;; //   '--;    | Gin-N-Tonic   endurance horse
 '  ;\    |      | Luv on Fire   trusty trail horse

 
 
 

1. I cannot get Shadow-3.3.1 to create shadow passwd file

  I am running Linux 1.1.70.  I have Shadow-3.1.1 patched with
Shadow-3.1.1-2.dif.  It compiles fine. ('make' and 'make install' used)  BUT
it does not convert my etc/passwd and create a shadowed file, nor are the 16
character passwords in effect.  My syslog is shows login giving a message of:
no shadow password found for 'userbob'.  I can login in fine, just no shadowed
passwords.

  I've noticed a pwconvert program being used for other OSs, but the Linux
patch does not result in one.  Can someone please tell me what I am missing?


2. Connecting machines via ethernet

3. Convert NIS passwd back to standard /etc/passwd & /etc/shadow

4. Help with gdb!

5. changing passwd on NIS server updates /etc/shadow only and not shadow.byname map

6. YP client calls

7. Shadow password files vs. non-shadowed passwords

8. Mosaic 2.1 can't start

9. getting passwd in C, SunOS with shadowed passwords

10. 4.1.x passwd -> 2.x passwd & shadow

11. shadow+passwd->passwd script

12. rconsiling the /etc/shadow and /etc/passwd files

13. Problem in passwd/shadow file