From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24546 invoked from network); 31 Dec 2020 22:59:23 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 31 Dec 2020 22:59:23 -0000 Received: (qmail 7942 invoked by uid 89); 31 Dec 2020 22:59:45 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 7933 invoked from network); 31 Dec 2020 22:59:45 -0000 X-Originating-IP: [82.21.120.173] X-Authenticated-User: J.deBoynePollard-newsgroups@NTLWorld.COM X-Spam: 0 X-Authority: v=2.3 cv=VOHzYeHX c=1 sm=1 tr=0 a=ZwFDrNcBZCEFJ5/d6y5G6w==:117 a=ZwFDrNcBZCEFJ5/d6y5G6w==:17 a=IkcTkHD0fZMA:10 a=rg2V61WcAAAA:8 a=RgxaCsPwAAAA:8 a=oGDxNFxvpK_dz2frFPoA:9 a=QEXdDO2ut3YA:10 a=2VPPlT2moWEA:10 a=Zzyutggc20oA:10 a=h2Zpg1Gm_F5nnxfnuFwt:22 a=SWuQIp9ssXIudwRe-5Wh:22 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1609455555; bh=a8y9Dzk0SJzr1yJg+JkNmMHdNZs3JFrzLPIje3VLLTY=; h=Subject:To:References:From:Date:In-Reply-To; b=B45aSJaFUbELvz3UXOZYj+h/DbcinyaFVy7RCjyLINRdP4Q2fCc3YvD7Xp0te+LFF DMqf4vvmxadN8TP8+rITBjPT1sqcbyPeDJRcxFjKMbBHYw6CPNh5PYf74maLwXxff5 rghsokw6LzeKTdxixJLbKogfTc0KnfjjwVXbMiIGy+BTB1yuHffiAASja6LIu/xn2j hE1fZUPh8awfTmHHgMcvNajkkxSjqe7B0iT4YoLRUWLg6tO+qOB1XHoROuK/+SyCWy sP+xEtC6H1hlqpOp+lEaNgtXFfP6s1uiKQ1s1k/VBqng2sL/uYUz2aUACCuKmKjb2d WCPHY4u5vWP9Q== Subject: Re: Why are there 3 programs in s6 that do the same thing? To: supervision References: From: Jonathan de Boyne Pollard Message-ID: Date: Thu, 31 Dec 2020 22:59:05 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfMM1W1piSBxXdLfTgwq0Z4iqfzjGSLOjTh7MCGEI9jSk1qLbadITyKvTLbZ2Zvpqu2lg9N6F/wFU6YIfZsGW1/lVbne00YeDZ/fLBFP5dhjRRBw1cUHe 9aLnyDLVM21W/L4NWOA+Ld9wJmuC9ssFZeox+BoPxzLml+B/znqLSEbASwhkb42j9w/yUC4Ygm3StZ9d4yG8yvszJft1m0iaZoz1Rkus2Ty1YDzYkyCrZFlt Laurent Bercot: > [...] direct adaptations from daemontools' setuidgid and envuidgid [...] > There is a similar history, and a similar spread of tools in the nosh toolset for roughly the same reasons. There was a need for a split toolset where one could look up things in the system account database, do stuff (in particular stuff that obscured access to the system account database), and then later change the process user/group IDs. There was also a need for tools that did not manipulate the user ID but only the group IDs. Hence envgid, envuidgid, getuidgid, setgid-fromenv, and setuidgid-fromenv; with setuidgid effectively being envuidgid followed by setuidgid-fromenv (except that it does not touch the environment). Uwe Ohse did the first setuidgid-fromenv tool, I believe, as a patch to daemontools back in 2001. Several people have developed tools in this way. * http://jdebp.uk./Softwares/nosh/guide/commands/setuidgid.xml * http://jdebp.uk./Softwares/nosh/guide/commands/envuidgid.xml * https://ohse.de/uwe/patches.html