depends rules for the manpages
-Check for all tools which variables are used.
-
Check all the expiry semantics
Add options --crypt-method and --sha-rounds to gpasswd
-method => algorithm in manpages
-
ALL:
- move base passwd/shadow/group/gshadow operation to module for allow write
different backend modules for db, NIS, LDAP and others. Default backend it
passwd have old piece of code with handling -r option and it will be good
finish this and propagate on other shadow tools for allow operate on other
user databases by well known tools.
-- Add/check support for split group
- Maybe that feature can be supported in gr_open/gr_close, with a variable
- in login.defs.
- useradd:
- add handle create user mail spool in maildir format.
- groupmems: check reason for isgroup
-- chgpasswd: uses chpasswd's pam config file. Why?
-
-- newusers: i = 100; no a nice initial value, use login.defs
+- newusers: i = 100; not a nice initial value, use login.defs
- newusers: doc for pw_gid not clear. Differentiate
pw_gid specified and exist