Date: Wed, 13 Mar 2002 14:00:03 -0800 (PST) From: Giorgos Keramidas <keramida@freebsd.org> To: freebsd-bugs@FreeBSD.org Subject: Re: i386/35816: no one can change password, because "passwd DB is locked" Message-ID: <200203132200.g2DM03n33980@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/35816; it has been noted by GNATS.
From: Giorgos Keramidas <keramida@freebsd.org>
To: Dima Dorfman <dima@trit.org>
Cc: "Crist J. Clark" <cjc@freebsd.org>, bug-followup@freebsd.org
Subject: Re: i386/35816: no one can change password, because "passwd DB is locked"
Date: Wed, 13 Mar 2002 20:54:42 +0200
On 2002-03-13 11:23, Dima Dorfman wrote:
> What happens if the data for that user changes between the time the
> editor is started (with the old info filled in) and the time the user
> is done editing? Assuming all the changes are valid, it would still
> be technically okay to apply the new changes, but it might come as a
> surprise to one or both of the parties involved.
>
> The above is intended as food for thought, not a flat-out rejection of
> your idea; it isn't clear whether this should be allowed to happen, or
> what we should do if it does.
Nice food for thought too. Imagine of the following scenario, on a machine
where two humans have root access:
- User A runs 'chpass foo'.
- Before user A finishes, user B runs 'chpass foo' too.
- User A deletes account of user C.
- User B adds account of user D.
- User A commits changes.
- User B commits changes.
Is the account of C still erased?
Giorgos Keramidas FreeBSD Documentation Project
keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203132200.g2DM03n33980>