On Sun 2021-02-28 (08:25), J. Hellenthal wrote:
> If it wasn???t ports then it was buildworld where it asks you ... would you
> like to run this now ? And you probably selected no instead of yes. Or some
> combination of that and mergemaster not being run.
Sure, though I'm always careful with bu
If it wasn’t ports then it was buildworld where it asks you ... would you like
to run this now ? And you probably selected no instead of yes. Or some
combination of that and mergemaster not being run.
--
J. Hellenthal
The fact that there's a highway to Hell but only a stairway to Heaven says
On Sun 2021-02-28 (12:12), Lehel Bernadt wrote:
> So first, regenerate the db files by running
> "pwd_mkdb -p /etc/master.passwd"
Hi, thanks yes I've run this and the user is back, but I'm more concerned with
how this happened.
___
freebsd-security@free
On Sun, Feb 28, 2021 at 10:58:08AM +0200, Gareth de Vaux wrote:
On Sat 2021-02-27 (18:12), J. Hellenthal wrote:
Looks like your master passwd db is out of sync.
Command is mkpwdb or something similar then run init q
Personally it would seem someone got ahold of master.passwd and doesn???t know
On Sat 2021-02-27 (18:13), J. Hellenthal wrote:
> Also
>
> ls -l /etc/*pass*
>
> Should show you those. Appears you've missed them.
# ls -l /etc/*pass*
-rw--- 1 root wheel 4092 Jan 23 12:22 /etc/master.passwd
-rw-r--r-- 1 root wheel 2621 Jan 23 12:22 /etc/passwd
__
On Sat 2021-02-27 (18:12), J. Hellenthal wrote:
> Looks like your master passwd db is out of sync.
>
> Command is mkpwdb or something similar then run init q
>
> Personally it would seem someone got ahold of master.passwd and doesn???t
> know how it works or a port upgrade failed to complete pro
