public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Daan De Meyer <daan.j.demeyer@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/setup] update_services: Insist that the root and nobody groups have the expected GIDs
Date: Mon, 22 Jun 2026 15:56:31 GMT	[thread overview]
Message-ID: <178214379169.1.7595728507506629721.rpms-setup-e34262181268@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/setup
            Branch : update_services
            Commit : e342621812686a5102f822a5873473203874236c
            Author : Daan De Meyer <daan.j.demeyer@gmail.com>
            Date   : 2025-03-20T12:08:48+01:00
            Stats  : +13/-13 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/setup/c/e342621812686a5102f822a5873473203874236c?branch=update_services

            Log:
            Insist that the root and nobody groups have the expected GIDs

This mirrors the same change from 49bb7fe5f88fc35b8529d7d8dfcd4c151a9aaf1a
and 4ced52595f3e0367a0f2823be8b7acf6d7b7c2be in systemd. Instead of potentially
allocating random GIDs for the root and nobody groups, let's insist that these
have the expected GIDs.

---
diff --git a/setup.sysusers.conf b/setup.sysusers.conf
index ee75bdc..82be285 100644
--- a/setup.sysusers.conf
+++ b/setup.sysusers.conf
@@ -1,16 +1,16 @@
-u root         0      "Super User"            /root            /bin/bash
-u bin          1      "bin"                   /bin             -
-u daemon       2      "daemon"                /sbin            -
-u adm          3:4    "adm"                   /var/adm         -
-u lp           4:7    "lp"                    /var/spool/lpd   -
-u sync         5:0    "sync"                  /sbin            /bin/sync
-u shutdown     6:0    "shutdown"              /sbin            /sbin/shutdown
-u halt         7:0    "halt"                  /sbin            /sbin/halt
-u mail         8:12   "mail"                  /var/spool/mail  -
-u operator    11:0    "operator"              /root            -
-u games       12:100  "games"                 /usr/games       -
-u ftp         14:50   "FTP User"              /var/ftp         -
-u nobody   65534      "Kernel Overflow User"  -                -
+u root         0:0     "Super User"            /root            /bin/bash
+u bin          1       "bin"                   /bin             -
+u daemon       2       "daemon"                /sbin            -
+u adm          3:4     "adm"                   /var/adm         -
+u lp           4:7     "lp"                    /var/spool/lpd   -
+u sync         5:0     "sync"                  /sbin            /bin/sync
+u shutdown     6:0     "shutdown"              /sbin            /sbin/shutdown
+u halt         7:0     "halt"                  /sbin            /sbin/halt
+u mail         8:12    "mail"                  /var/spool/mail  -
+u operator    11:0     "operator"              /root            -
+u games       12:100   "games"                 /usr/games       -
+u ftp         14:50    "FTP User"              /var/ftp         -
+u nobody   65534:65534 "Kernel Overflow User"  -                -
 g root           0
 g sys            3
 g adm            4

                 reply	other threads:[~2026-06-22 15:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178214379169.1.7595728507506629721.rpms-setup-e34262181268@fedoraproject.org \
    --to=daan.j.demeyer@gmail.com \
    --cc=git-commits@fedoraproject.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