#248130 adduser: GROUPDIRS support

Package:
adduser
Source:
adduser
Submitter:
Christian Gatzemeier
Date:
2026-06-17 20:03:01 UTC
Severity:
wishlist
Tags:
#248130#5
Date:
2004-05-09 14:06:34 UTC
From:
To:
This goes along the same lines as the --template option, it
tries to facilitate managing multiple users efficiently.

Please consider supporting creation of goup directories
upon non-system group creation just like creating home
directories upon user creation.

For example:
DGROUPDIR=/group
QUOTAGROUP=
GROUP_DIR_MODE=2775


BTW: What are the "bad side effects" of SETGID_HOME noted
in the config file and what benefit did it give?


Concerning the adduser rewrite for mutiple backend
and frontend support, maybe you'll be interested in
investigating the simmilar concepts of Config4GNU.

http://freedesktop.org/Software/CFG

Regards,
Christian
#248130#10
Date:
2011-11-23 10:56:26 UTC
From:
To:
I would review and probably apply a patch doing this.

I guess that nobody remembers any more. The change was made by Roland
eleven years ago.

Greetings
Marc
#248130#13
Date:
2011-11-23 10:56:26 UTC
From:
To:
I would review and probably apply a patch doing this.

I guess that nobody remembers any more. The change was made by Roland
eleven years ago.

Greetings
Marc
#248130#18
Date:
2022-07-26 08:24:00 UTC
From:
To:
Answer comes a bit late, but building a container image, software
archive, chroot etc in an sgid set directory might have group names
propagate into the archive and systems where it is unpacked.

Unpack an arbitrary software relese tarball in an sgid home directory
and tar it up again and see group ownership changed. That comes
surprising for many users, so we think that it should be the decision of
the local admin to set the local default to "sgid home directories".

As to the original request, we do not currently plan to work on this,
but will consider Merge Requests including documentation and test cases.

Greetings
Marc
#248130#21
Date:
2022-07-26 08:24:00 UTC
From:
To:
Answer comes a bit late, but building a container image, software
archive, chroot etc in an sgid set directory might have group names
propagate into the archive and systems where it is unpacked.

Unpack an arbitrary software relese tarball in an sgid home directory
and tar it up again and see group ownership changed. That comes
surprising for many users, so we think that it should be the decision of
the local admin to set the local default to "sgid home directories".

As to the original request, we do not currently plan to work on this,
but will consider Merge Requests including documentation and test cases.

Greetings
Marc