Date: Sat, 08 Mar 2014 10:22:36 +1100 From: Joe Shevland <joe.shevland@internode.on.net> To: =?UTF-8?B?TWFya28gQ3VwYcSH?= <marko.cupac@mimar.rs>, freebsd-stable@freebsd.org Subject: Re: passwd(1) weirdness... Message-ID: <531A54BC.4000405@internode.on.net> In-Reply-To: <20140307201047.5ffdaaa8aa36c78c7baf23a2@mimar.rs> References: <5319EE35.5070108@freebsd.org> <20140307201047.5ffdaaa8aa36c78c7baf23a2@mimar.rs>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/03/2014 6:10 AM, Marko Cupać wrote: > On Fri, 07 Mar 2014 16:05:09 +0000 > Matthew Seaman <matthew@freebsd.org> wrote: > >> Has anyone else seen an affect like this? >> >> We have a couple of machines running 9.2-RELEASE-p3 recently upgraded >> from 9.1-RELEASE-pX via freebsd-update. >> >> On attempting to change a user's password via passwd(1), everything >> apparently works fine; no sign of any errors and the password hash in >> /etc/master.passwd is changed -- but the user cannot log in with the >> new password *until* 'pwd_mkdb -p' is run manually. > Now when you mention it I am starting to think I haven't actually been > dreaming. I have seen it. Suspicious :) Possibly the NSA dropped the ball on intercepting it and didn't update the shadow file appropriately.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?531A54BC.4000405>