From: Joshua Branson <jbranso@fastmail.com>
To: 31814@debbugs.gnu.org
Subject: bug#31814: setuid programs are not first in PATH
Date: Thu, 14 Jun 2018 10:01:07 -0400 [thread overview]
Message-ID: <87vaaltql8.fsf@fastmail.com> (raw)
In-Reply-To: <877en24tf2.fsf@lassieur.org> ("Clément Lassieur"'s message of "Wed, 13 Jun 2018 17:06:57 +0200")
Clément Lassieur <clement@lassieur.org> writes:
> Joshua Branson <jbranso@fastmail.com> writes:
>
>> Clément Lassieur <clement@lassieur.org> writes:
>>
>>> Hi,
>>>
>>> sourcing /etc/profile
>>>
>>> - prepends /run/setuid-programs to $PATH
>>> - then sources $HOME/.guix-profile/etc/profile
>>>
>>> and sourcing $HOME/.guix-profile/etc/profile
>>>
>>> - prepends $HOME/.guix-profile/bin to $PATH
>>> - prepends $HOME/.guix-profile/sbin to $PATH
>>>
>>> so in the end, $PATH looks like:
>>>
>>> ~/.config/guix/current/bin:~/.guix-profile/bin:~/.guix-profile/sbin:/run/setuid-programs:...
>>>
>>> and a command like 'ping' is found in ~/.guix-profile/bin, which makes
>>> it unusable.
>>
>> I'm probably being really silly, but shouldn't it still work? I mean
>> ~/.guix-profile/bin is still in your path right?
>
> Yes, but ~/.guix-profile/bin/ping (which is the one being chosen)
> doesn't have the setuid flag, so it doesn't work.
Oh. I didn't realize that the ping command was a setuid program. cool.
next prev parent reply other threads:[~2018-06-14 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 14:32 bug#31814: setuid programs are not first in PATH Clément Lassieur
2018-06-13 15:05 ` Joshua Branson
2018-06-13 15:06 ` Julien Lepiller
2018-06-13 15:06 ` Clément Lassieur
2018-06-14 14:01 ` Joshua Branson [this message]
2018-06-16 9:35 ` Ricardo Wurmus
2018-06-16 22:35 ` Clément Lassieur
2018-06-17 21:07 ` Ludovic Courtès
2018-06-18 6:16 ` Clément Lassieur
2018-06-19 9:29 ` Ludovic Courtès
2018-06-19 10:26 ` Clément Lassieur
2018-06-18 13:40 ` Marius Bakke
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=87vaaltql8.fsf@fastmail.com \
--to=jbranso@fastmail.com \
--cc=31814@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 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).