From: Saku Laesvuori <saku@laesvuori.fi>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Josselin Poiret <dev@jpoiret.xyz>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Setuid handling?
Date: Tue, 25 Apr 2023 20:04:22 +0300 [thread overview]
Message-ID: <20230425170422.66rd4ro4gblngbc7@X-kone> (raw)
In-Reply-To: <CAFHYt55HEGpR__ub-nB_5EN+XwPDs+zzBjCyqk3Ar6Bc7OVVZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
> > /run/setuid-programs/ should be at the top of your PATH.
>
> Well, the home profile ends up being first here:
I, too, have my home profile as the first one. Having peeked into
/etc/profile and ~/.guix-home/setup-environment it seems like that is
the original order without any interference from the user's shell
configuration.
> > The default /etc/profile should ensure that
The default /etc/profile only ensures that when the user profile is
~/.guix-profile or ~/.config/guix/current. Guix home stores the profile
at ~/.guix-home/profile.
> Thanks for that pointer! I'm in Bash, via Eat. [1] Right now I'm not
> sure where to look, so more references from anybody would be
> appreciated.
Maybe you could remove the packages with setuid-programs from your home
configuration, but really this seems like a bug in guix home to me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-25 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 1:02 Setuid handling? Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-25 12:25 ` Josselin Poiret
2023-04-25 14:32 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-25 15:37 ` Josselin Poiret
2023-04-25 16:21 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-25 16:50 ` Leo Famulari
2023-04-25 17:04 ` Saku Laesvuori [this message]
2023-05-17 4:37 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230425170422.66rd4ro4gblngbc7@X-kone \
--to=saku@laesvuori.fi \
--cc=dev@jpoiret.xyz \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).