Hi,
"pelzflorian (Florian Pelz)" <pelzflor...@pelzflorian.de> skribis:
> On Mon, Jun 03, 2019 at 03:22:51PM +0200, Ludovic Courtès wrote:
>> > After multiple reconfigures, it happened again, my /etc/shadow has !
>> > again in the password field. My recently changed root password became
>> > empty as well, like 35902. I did not even run sudo concurrently. The
>> > password just got locked.
>>
>> What were the differences between your config files when you
>> reconfigured?
>>
>
> For the last reconfigure, there were no differences, although I had
> rebooted into an unbootable, older generation with a different
> syslog.conf and broken Udevd arguments before booting the new
> generation.
What’s the effect of this brokenness concretely? Is the wrong root file
system mounted, or something like that?
Could it somehow lead Guix to stumble upon an empty or missing
/etc/shadow when it boots?
> I suppose the other victims of this bug have not booted to unbootable
> generations?
It’d be great if the other victims would speak up. :-)
> If locks do not stop these issues, it would be nice to have more
> detailed logs of shadow changes written to syslog on reconfigure
> and/or on reboot.
There really isn’t much to log: the activation code reads
/etc/{shadow,passwd,group}, computes the list of shadow/passwd/group
entries as a function of that, and writes it.
Ludo’.
