public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] dynamic groups and users
Date: Thu, 01 Aug 2019 22:47:28 +0200	[thread overview]
Message-ID: <0797f90fd71fdcf9b1c3632f54d3ddf8f3ebddc1.camel@gentoo.org> (raw)
In-Reply-To: <76000f9a-31ac-f652-797a-d7494edac176@uls.co.za>

[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]

On Thu, 2019-08-01 at 21:04 +0200, Jaco Kroon wrote:
> Hi,
> 
> Looking at the new eclasses for acct-user and acct-group.
> 
> These enforce that a group and user id should be set.
> 
> This is not a requirement for enewuser nor enewgroup.
> 
> As a further discrepancy, the user eclass requires >0 for the IDs, 
> whereas the checks in acct-user and acct-group is for >= 0.
> 
> Would it be ok to suggest that we allow -1 (or 0, but that could be 
> confused with the root user/group) in acct-user and acct-group to 
> specify "no specific id, please allocate dynamically"?
> 
> Use case:  I'm building some experimental packages in an overlay, and I 
> really don't care what the UID and GID values are, I just need something 
> unique on the host I can use to avoid running the service as root.  
> Guessing I could just manually useradd -r but then again ... if I do 
> later submit these into the main tree (or other packages) then it 
> becomes a problem, and maintaining acct-{user,group}/* outside of main 
> tree could conflict with main tree at a later stage ... either way, 
> having some way to say "I honestly don't care, just give me a random 
> number" is probably a good thing.
> 

I'll look into adding support for '-1' in a few days.  However, I'm
going to add QA checks to prevent it from getting into ::gentoo first.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  parent reply	other threads:[~2019-08-01 20:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 19:04 [gentoo-dev] dynamic groups and users Jaco Kroon
2019-08-01 20:01 ` Mike Gilbert
2019-08-01 20:22   ` Jaco Kroon
2019-08-02 16:33   ` Mike Gilbert
2019-08-01 20:47 ` Michał Górny [this message]
2019-08-02  9:14   ` Jaco Kroon
2019-08-02  9:53     ` Michał Górny
2019-08-02 15:46       ` Michael Orlitzky
2019-08-02 15:58         ` Michał Górny
2019-08-02 16:24           ` Michael Orlitzky
2019-08-02 17:06             ` Michał Górny
2019-08-04 16:22               ` Jaco Kroon
2019-08-06 11:41                 ` Jaco Kroon
2019-08-07 15:48                   ` Michał Górny
2019-08-08  6:52                     ` Jaco Kroon
2019-08-08  8:42                     ` Ulrich Mueller
2019-08-08 10:04                       ` Jaco Kroon
2019-08-03  0:53             ` James Cloos
2019-08-17 20:38 ` Michał Górny

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=0797f90fd71fdcf9b1c3632f54d3ddf8f3ebddc1.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.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