積丹尼 Dan Jacobson <[email protected]> writes: > Problem: each upgrade locks nobody
> # su nobody > This account is currently not available. Giving nobody a valid shell makes me absolutely cringe from a security standpoint, but it's your system and you can do what you want with it, obviously. Still, really not a wise thing to do. > Solution: > Reconfigure package. > # debconf-show base-passwd|grep nobody > base-passwd/system/user/nobody/shell/_bin_bash/_usr_sbin_nologin: true > base-passwd/system/user/nobody/shell/_bin_sh/_usr_sbin_nologin: true > # dpkg-reconfigure --priority=low base-passwd > # > Conclusion: no way to access those configuration variables. The configuration variables don't control whether nobody has a valid shell. They control whether or not base-passwd changes what the shell is set to if it thinks the shell is wrong. So, change the shell in /etc/passwd, and *then* run dpkg-reconfigure. You should get prompted for whether you want to let update-passwd change the shell back. Say no, and that response will be remembered for all subsequent upgrades. The problem you're having right now is that you're running dpkg-reconfigure while the shell is correct as far as base-passwd is concerned, which means that there's nothing for it to ask about. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
