From: Jan Braun <janbraun@gmx.de>
To: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
Cc: supervision@list.skarnet.org
Subject: Re: chpst -u and supplementary groups
Date: Tue, 20 Aug 2019 12:04:33 +0200 [thread overview]
Message-ID: <20190820100433.rlioufyvxodvwkpc@klumpi.ignorelist.com> (raw)
In-Reply-To: <1222e286-60ed-4790-7aa9-6c4f78c52cd0@NTLWorld.COM>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
Jonathan de Boyne Pollard schrob:
> > My inability to see the issue came from the fact that all other similar
> > programs (I'm aware of) do in fact add the supplementary groups.
> >
> Then you are not aware of Bernstein daemontools, where setuidgid does not.
> (-:
Well, I am aware of their existance, but I've never used them, only
various descendants. I even suspected they might not handle
supplementary groups, because e.g. s6-envuidgid introduces GIDLIST to
deal with them.
> Setting only one group was the behaviour of the original tool. Setting the
> supplementary groups as well is behaviour that others added to their
> toolsets later. Bruce Guenter (in daemontools-encore) and I added it as an
> optional behaviour for setuidgid.
Yes. Apparently everyone re-implementing daemontools does something like
this. So that brings me back to my original question: is there consensus
that the historical behaviour is a bug? Or are there valid use cases¹?
cheers,
Jan
¹) Besides when the account has no supplementary groups, obviously.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-20 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 12:08 Jan Braun
2019-08-19 19:33 ` Steve Litt
2019-08-19 22:06 ` Bougy Man
2019-08-20 7:25 ` Jonathan de Boyne Pollard
2019-08-20 10:04 ` Jan Braun [this message]
2019-08-20 18:21 ` Laurent Bercot
2019-08-21 3:50 ` Jan Braun
2019-08-20 18:25 ` Cameron Nemo
2019-08-21 3:22 ` Jan Braun
2019-08-21 22:26 ` Steve Litt
2019-08-27 23:44 Jeff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190820100433.rlioufyvxodvwkpc@klumpi.ignorelist.com \
--to=janbraun@gmx.de \
--cc=J.deBoynePollard-newsgroups@NTLWorld.COM \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).