From owner-cvs-all Sun Mar 17 18:23: 2 2002 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 319E937B416; Sun, 17 Mar 2002 18:22:54 -0800 (PST) Received: (from cjc@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2I2Ms309830; Sun, 17 Mar 2002 18:22:54 -0800 (PST) (envelope-from cjc) Message-Id: <200203180222.g2I2Ms309830@freefall.freebsd.org> From: "Crist J. Clark" Date: Sun, 17 Mar 2002 18:22:53 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/usr.bin/chpass chpass.c pw_copy.c pw_copy.h X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cjc 2002/03/17 18:22:53 PST Modified files: usr.bin/chpass chpass.c pw_copy.c pw_copy.h Log: It was possible for an unprivileged user to tie up the password information (no one else can vipw(8), chpass(1), or even passwd(1)), either on purpose or by accident, until an administrator manually intervened. Instead, do not lock the master.passwd file while a user is editing his information. But once we go to write the new information, check that the modified user's information has not changed in the password database since we started. Abort the changes if it has. Add a $FreeBSD$ to pw_copy.h. PR: i386/35816 Obtained from: NetBSD MFC after: 1 week Revision Changes Path 1.19 +29 -22 src/usr.bin/chpass/chpass.c 1.11 +34 -2 src/usr.bin/chpass/pw_copy.c 1.2 +2 -2 src/usr.bin/chpass/pw_copy.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message