From: "Alexandru-Sergiu Marton" <brown121407@posteo.ro>
To: Efraim Flashner <efraim@flashner.co.il>,
Alexandru-Sergiu Marton <brown121407@member.fsf.org>
Cc: 40550@debbugs.gnu.org
Subject: bug#40550: zsh: sudo is not setuid
Date: Mon, 13 Apr 2020 07:46:58 +0300 [thread overview]
Message-ID: <C1ZT2LM0ATS0.3LWS5KNCFSPWV@121408> (raw)
In-Reply-To: <20200411193821.GB2191@E5400>
On Sun Apr 12, 2020 at 1:38 AM PST, Efraim Flashner wrote:
> Do you have sudo installed in a profile? /run/setuid-programs/sudo
> should be the first 'sudo' in your PATH regardless of the shell. What's
> the contents of your $PATH?
This is my $PATH in zsh:
/home/brown/bin:/home/brown/.local/bin:/home/brown/.guix-profile/bin:/home/brown/.guix-profile/sbin:/run/current-system/profile/bin
> (ins)efraim@E5400 ~$ which -a sudo
> /run/setuid-programs/sudo
> /run/current-system/profile/bin/sudo
$ which -a sudo
/run/current-system/profile/bin/sudo
BUT!
$ ls /run/setuid-programs/
dbus-daemon-launch-helper newuidmap pkexec sudoedit
fusermount passwd polkit-agent-helper-1 umount
mount ping su
newgidmap ping6 sudo
So it looks like it's a problem with my PATH. While in bash I don't
append /run/setuid-programs to it manually, yet bash recognizes the
setuid programs. I'll probably add /run/setuid-programs by hand but I'm
wondering why doesn't it work by default.
Thanks,
Sergiu
next prev parent reply other threads:[~2020-04-13 4:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 10:10 bug#40550: zsh: sudo is not setuid Alexandru-Sergiu Marton
2020-04-11 19:38 ` Efraim Flashner
2020-04-13 4:46 ` Alexandru-Sergiu Marton [this message]
2020-04-13 5:01 ` Alexandru-Sergiu Marton
2020-04-13 17:55 ` Leo Famulari
2020-04-13 19:14 ` Leo Famulari
2020-04-17 5:45 ` Alexandru-Sergiu Marton
2020-04-17 7:58 ` Alexandru-Sergiu Marton
2020-04-17 14:44 ` Efraim Flashner
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=C1ZT2LM0ATS0.3LWS5KNCFSPWV@121408 \
--to=brown121407@posteo.ro \
--cc=40550@debbugs.gnu.org \
--cc=brown121407@member.fsf.org \
--cc=efraim@flashner.co.il \
/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.