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

Attachment: signature.asc
Description: Digital signature

Reply via email to