From: Ulrich Mueller <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)
Date: Mon, 09 Dec 2019 10:44:04 +0100 [thread overview]
Message-ID: <w6g1rtd3kbf.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <84a435bffe460efd2620ceec0c0405fa18a7937b.camel@gentoo.org> ("Michał Górny"'s message of "Mon, 09 Dec 2019 09:17:45 +0100")
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
>>>>> On Mon, 09 Dec 2019, Michał Górny wrote:
> My proposal would be to:
> a. split the UID/GID range into 'high' (app) and 'low' (system)
> assignments, 'high' being >=100 and 'low' <100 (matching Apache suEXEC
> defaults),
Good, but can we make these ranges more explicit please, like 100..499
for "high" and 0..99 for "low"? (But 100 is special too, I guess?)
> b. UIDs/GIDs in the 'high' range can be taken arbitrarily
> (recommending taking highest free),
I'd say something like this:
"b. UIDs/GIDs in the 'high' range can be taken arbitrarily and are
assigned on a FCFS basis. IDs used upstream or by other distros can
serve as a loose guideline. Otherwise, taking the highest free number
in the range is recommended."
> while in the 'low' range must be approved by QA,
> c. no review requirement for the 'high' range, just choose your
> UID/GID straight of uid-gid.txt and commit it,
> d. strong recommendation to use matching UID/GID for the same
> user/group name.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-12-09 9:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 8:17 [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing) Michał Górny
2019-12-09 9:44 ` Ulrich Mueller [this message]
2019-12-09 10:00 ` Ulrich Mueller
2019-12-09 16:54 ` Thomas Deutschmann
2019-12-09 17:47 ` Ulrich Mueller
2019-12-09 18:02 ` Thomas Deutschmann
2019-12-09 18:48 ` Ulrich Mueller
2019-12-09 20:10 ` Thomas Deutschmann
2019-12-10 14:36 ` Michael Orlitzky
2019-12-09 21:48 ` Alec Warner
2019-12-10 5:28 ` Michał Górny
2019-12-10 5:44 ` Joonas Niilola
2019-12-10 11:47 ` Rich Freeman
2019-12-10 12:26 ` Thomas Deutschmann
2019-12-10 12:44 ` Rich Freeman
2019-12-10 13:25 ` Thomas Deutschmann
2019-12-10 13:48 ` Rich Freeman
2019-12-10 16:05 ` Joonas Niilola
2019-12-10 16:25 ` Michael Orlitzky
2019-12-10 13:34 ` Michał Górny
2019-12-10 16:13 ` Joonas Niilola
2019-12-10 16:17 ` Michał Górny
2019-12-10 14:50 ` Michael Orlitzky
2019-12-10 15:04 ` Michał Górny
2019-12-10 15:54 ` Rich Freeman
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=w6g1rtd3kbf.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.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