From: Dariqq <dariqq@posteo.net>
To: 73680@debbugs.gnu.org
Subject: bug#73680: privileged-programs: cant set setuid/setgid to new accounts/groups
Date: Wed, 9 Oct 2024 16:35:36 +0000 [thread overview]
Message-ID: <26df374b-5cc8-4512-b276-05df5d4d2b6a@posteo.net> (raw)
In-Reply-To: <82936b4e-f572-407a-a98d-1d5771c6ec37@posteo.net>
The problem is the ordering of the services which is responsible for the
order in the activation-service-type after folding:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/system.scm#n808
It currently looks something like this (omitting some things)
activation-service
...
account-service
etc-service
...
privileged-program-service
---
which are added to the folded activation-service in reverse order (one
can check this by looking at the service-value of
(fold-services (operating-system-services %os) #:target-type
activation-service-type)
I think the easiest solution would be to either move the
privileged-program-service-type up or the account-service down.
Because activation-service is above account-service users/groups are
already available for direct activation-service extensions that set
permission/ownership on files
next prev parent reply other threads:[~2024-10-09 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:55 bug#73680: privileged-programs: cant set setuid/setgid to new accounts/groups Dariqq
[not found] ` <handler.73680.B.17283129493491.ack@debbugs.gnu.org>
2024-10-07 20:31 ` bug#73680: Acknowledgement (privileged-programs: cant set setuid/setgid to new accounts/groups) Dariqq
2024-10-08 10:45 ` bug#73680: privileged-programs: cant set setuid/setgid to new accounts/groups Dariqq
2024-10-09 16:35 ` Dariqq [this message]
2024-10-09 18:08 ` Dariqq
2024-10-12 8:20 ` Dariqq
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=26df374b-5cc8-4512-b276-05df5d4d2b6a@posteo.net \
--to=dariqq@posteo.net \
--cc=73680@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.