From owner-freebsd-commit  Sun Aug 13 09:12:38 1995
Return-Path: commit-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id JAA29459
          for commit-outgoing; Sun, 13 Aug 1995 09:12:38 -0700
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id JAA29446
          for cvs-usrbin-outgoing; Sun, 13 Aug 1995 09:12:35 -0700
Received: (from wpaul@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id JAA29436
          ; Sun, 13 Aug 1995 09:12:30 -0700
Date: Sun, 13 Aug 1995 09:12:30 -0700
From: Bill Paul <wpaul>
Message-Id: <199508131612.JAA29436@freefall.FreeBSD.org>
To: CVS-commiters, cvs-usrbin
Subject: cvs commit: src/usr.bin/chpass pw_yp.c pw_yp.h Makefile chpass.1 chpass.c edit.c pw_copy.c
Sender: commit-owner@FreeBSD.org
Precedence: bulk

wpaul       95/08/13 09:12:29

  Modified:    usr.bin/chpass  Makefile chpass.1 chpass.c edit.c pw_copy.c
  Added:       usr.bin/chpass  pw_yp.c pw_yp.h
  Log:
  Take the ypchfn/ypchsh stuff that was removed from passwd
  and graft it into chpass.
  
  Chpass can now tell when it's being asked to operate on an NIS
  user and it displayes the appropriate message in the editor
  template ("Changing NIS information for foo"). After the changes
  have been made, chpass will promte the user for his NIS password.
  If the password is correct, the changes are committed to yppasswdd.
  
  Hopefully, this should make NIS more transparent to the end user.
  
  Note that even the superuser needs to know a user's password before
  he can change any NIS information (such is the nature of yppasswdd).
  Also, changes to the password field are not permitted -- that's what
  yppasswd is for. (The superuser may specify a new password, but
  again, he needs to know the user's original password before he can
  change it.)