* Andreas Henriksson <andr...@fatal.se> [170122 17:25]:
> [..]
> # chsh
> 
> shadow                                util-linux
> ================================================================
> -h (== --help)                        -u (== --help)
> 
> -R chroot-dir
> --root chroot-dir
> 
> (not listing the options only existing in util-linux)
> 
> 
> The strict validation of only valid shells allowed for non-root seems
> to be a COMPILE-TIME "opt-in" feature in util-linux version:
> --enable-chsh-only-listed
> (Default in util-linux is to just warn when setting shell not listed in 
> /etc/shells.)

>From a quick look at 2.29.1-1, it appears to be a compile-time
opt-out feature. From ./configure --help:
  --disable-chsh-only-listed
                          chsh: allow shells not in /etc/shells


> # newgrp
> 
> The optional command-line '-' in shadow not supported in util-linux version.
> 
> The shadow man page is much longer and describes possible additional 
> functionality in shadow version (this needs further investigation):
> 
> * password prompting
> * gshadow

u-l newgrp reads gshadow (and falls back to group) for the password,
and does password prompting, if a password is set.

> The shadow version has (compile-time optional) support for login.defs 
> variable SYSLOG_SG_ENAB but that's not available in (any) util-linux tool.

Note that in shadow, this is compile-time and run-time enabled in Debian.


> # vipw
> 
> The shadow version of vipw and vigr supports many command-line options, while 
> the util-linux equivalents only supports:
> 
> -h --help
> (-V --version)

The biggest issue I'm seeing there is the behaviour rgd. the shadow
files.
shadow vipw/vigr allow you to say --shadow to just edit the respective
shadow file.
u-l vipw/vigr do not have this flag, and interactively prompt after
editing the normal file, if the user wants to change the shadow
file too.

shadow vipw/vigr also have --passwd/--group, but personally I see no
value in supporting `vigr --passwd` ...

-- 
christian hofstaedtler <z...@debian.org>

Reply via email to