[Cpu-users] Group Changes and CPU 1.4.1-RC1

[Blake M. <bma...@pu...>]

CPU 1.4.1-RC1 is available at:
http://cpu.sourceforge.net/cpu-1.4.1-RC1.tar.gz
  and
http://cpu.sourceforge.net/cpu-1.4.1-RC1.tar.bz2

There have been several major changes made in terms of the behavior of cpu.
These include:
 - Refuse to add or modify users whose supplementary groups (or supplied
   primary groups) do not exist. This is the same behavior as the GNU
   shadowutils
 - When a user is deleted they are now automatically removed from any
   secondary groups they were in (same as shadow-utils).
 - When a users secondary groups are modified, they are removed from all old
   secondary groups and added to new secondary groups (same as shadow-utils).
 - When a users primary group is changed they are no longer added to that
   group via a memberUid (same as shadow-utils).
 - Refuse to perform a groupdel if the group is a users primary group. This is
   the default behavior of the shadow-utils. However, the shadow-utils allow
   the group id to be changed even if it is a users primary group. I think
   this is wrong, but cpu does the same thing. Should it?
 - Allow violation of POSIX naming conventions (for use with Samba) by
   specifying the -o switch

I would appreciate feedback if people think any of the above behaviors are
incorrect. The other thing I have been thinking about, is what the behavior
should be when a user is added and -g is not explicitly set. Should a group be
generated with the same name as the user, and make the users primary group
that? Should there be a setting in the configuration file that specifies a
default group?

As always, feedback (and bug-reports) are appreciated.

-Blake

-- 
Blake Matheny           "... one of the main causes of the fall of the
bma...@pu...      Roman Empire was that, lacking zero, they had
http://www.mkfifo.net    no way to indicate successful termination of
http://ovmj.org/GNUnet/  their C programs." --Robert Firth