summaryrefslogtreecommitdiffstats
path: root/usr.bin/chpass/pw_copy.h
diff options
context:
space:
mode:
authorcjc <cjc@FreeBSD.org>2002-03-18 02:22:53 +0000
committercjc <cjc@FreeBSD.org>2002-03-18 02:22:53 +0000
commited673bb689afdf58f832ec1485843b0bdf894d11 (patch)
treeae80c74d62d2ac0aef09586a5659dcc1230c0a08 /usr.bin/chpass/pw_copy.h
parent54cd426b9006a7048342920f73050a1dd9994cd0 (diff)
downloadFreeBSD-src-ed673bb689afdf58f832ec1485843b0bdf894d11.zip
FreeBSD-src-ed673bb689afdf58f832ec1485843b0bdf894d11.tar.gz
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
Diffstat (limited to 'usr.bin/chpass/pw_copy.h')
-rw-r--r--usr.bin/chpass/pw_copy.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/usr.bin/chpass/pw_copy.h b/usr.bin/chpass/pw_copy.h
index 4ef68c5..20f3bcc 100644
--- a/usr.bin/chpass/pw_copy.h
+++ b/usr.bin/chpass/pw_copy.h
@@ -30,7 +30,7 @@
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
- * @(#)pw_copy.h 8.1 (Berkeley) 4/2/94
+ * $FreeBSD$
*/
-void pw_copy __P((int, int, struct passwd *));
+void pw_copy __P((int, int, struct passwd *, struct passwd *));
OpenPOWER on IntegriCloud