Date: Wed, 13 Mar 2002 02:54:49 -0800 From: "Crist J. Clark" <cjc@FreeBSD.ORG> To: billf@FreeBSD.ORG Cc: irys@irc.pl, freebsd-bugs@FreeBSD.ORG Subject: Re: i386/35816: no one can change password, because "passwd DB is locked" Message-ID: <20020313025449.R29705@blossom.cjclark.org> In-Reply-To: <200203121143.g2CBhqd03584@freefall.freebsd.org>; from billf@FreeBSD.ORG on Tue, Mar 12, 2002 at 03:43:52AM -0800 References: <200203121143.g2CBhqd03584@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 12, 2002 at 03:43:52AM -0800, billf@FreeBSD.ORG wrote:
> Synopsis: no one can change password, because "passwd DB is locked"
>
> State-Changed-From-To: open->closed
> State-Changed-By: billf
> State-Changed-When: Tue Mar 12 03:41:48 PST 2002
> State-Changed-Why:
> this is not a bug. root can find the process that is holding the lock
> on the password database and kill both it and the user holding it.
This does look like a bug to me. I don't understand why chpass(1)
needs to hold a lock on the database while the user is editing his
entry. It seems like once the user is done editing, _then_ the
master.passwd can be locked, the user's modifications checked, and
then added if they are OK. Why would it need to be locked during the
editing process? I don't see a good reason looking at the code.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
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?20020313025449.R29705>