Your message dated Sun, 4 Feb 2018 15:50:56 +0100
with message-id <20180204145056.pcbxmlwxczdj2...@percival.namespace.at>
and subject line Re: #769743: fixed in stable
has caused the Debian Bug report #769743,
regarding sulogin segfaults if shadow passwords are not enabled
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
769743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysvinit-utils
Version: 2.88dsf-58
Severity: normal
I deployed a system accidentially without shadow passwords
enabled (all user accounts had * in /etc/passwd), and sulogin
failed with "sulogin: cannot open password database!"
It then segfaulted. Which is the bug.
Interestingly, systemd continued with the boot and the system
came up otherwise ok.
Note that this is perhaps a more common configuration than might be
expected. For example, when using systemd-nspawn on a debootstrapped
chroot, the container that is booted up is in exactly this
configuration. If for some reason the boot proceess of that container
needs to call sulogin, it will presumably fail the same way.
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Already fixed in stable, closing.
--- End Message ---
