[Pkg-shadow-devel] Bug#924505: bash: set shell to /bin/sh on removal

Dmitry Bogatov KAction at disroot.org
Sun Sep 8 20:16:27 BST 2019

[2019-09-03 22:21] Chris Hofstaedtler <zeha at debian.org>
> * Matthias Klose <doko at debian.org> [190903 17:37]:
> > On 02.09.19 21:14, Dmitry Bogatov wrote:
> > > Subject: [PATCH] Change shells of users from /bin/bash to /bin/sh on removal
> > 
> > sorry for joining in lately into this game, but I didn't want to do that in
> > parallel with my other Debian tasks.
> > 
> > I don't like the idea of automatic shell rewriting, [..]
> > For user accounts it potentially creates broken
> > init files, because the user's init files might use bashisms. The same might
> > be true for system accounts, although you can manually check if these
> > accounts use bashisms.  Nobody is hurt by having bash installed, you can
> > avoid that for new installations, so this change doesn't seem to have any
> > benefit which out weights the regression potential.  There also isn't any
> > precedence for other shells doing that.
> I also don't understand what the point of the whole exercise is;
Point of whole excersise is strip bash of essential flag.

> once you have user accounts that use bash, they should just stay as
> they were.

If so, removing bash, once it is no longer essencial, will break default
installation where root shell is bash. This is not how uninstallation is
intended to work.

> For new systems, defaulting to dash might be useful.

No. Firstly, many would object this change. Secondly, it does not solve
initial problem.
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

More information about the Pkg-shadow-devel mailing list