all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Alexandru-Sergiu Marton <brown121407@posteo.ro>
Cc: Alexandru-Sergiu Marton <brown121407@member.fsf.org>,
	40550@debbugs.gnu.org
Subject: bug#40550: zsh: sudo is not setuid
Date: Mon, 13 Apr 2020 13:55:55 -0400	[thread overview]
Message-ID: <20200413175555.GB23262@jasmine.lan> (raw)
In-Reply-To: <C1ZT2LM0ATS0.3LWS5KNCFSPWV@121408>

On Mon, Apr 13, 2020 at 07:46:58AM +0300, Alexandru-Sergiu Marton wrote:
> 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

Setting up Zsh should definitely work when creating a new user's home
directory, but maybe it doesn't do the right thing when changing a
user's shell after the home directory has already been created. We
should look into that.

Please copy the contents of '/etc/skel/.zprofile' to your zprofile file
and check for the /run/setuid-programs in your $PATH after logging in
again with `zsh --login`.

  parent reply	other threads:[~2020-04-13 17:57 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
2020-04-13  5:01     ` Alexandru-Sergiu Marton
2020-04-13 17:55     ` Leo Famulari [this message]
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=20200413175555.GB23262@jasmine.lan \
    --to=leo@famulari.name \
    --cc=40550@debbugs.gnu.org \
    --cc=brown121407@member.fsf.org \
    --cc=brown121407@posteo.ro \
    /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.