Github messages for voidlinux
 help / color / mirror / Atom feed
From: eli-schwartz <eli-schwartz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: users running unprivileged lxc container no worky no more.
Date: Wed, 17 Aug 2022 05:01:00 +0200	[thread overview]
Message-ID: <20220817030100.MwzcwQeSPDd0WEyTSH9FYYOMDr8EAIW7iK8G0d0AUVs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38682@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 506 bytes --]

New comment by eli-schwartz on void-packages repository

https://github.com/void-linux/void-packages/issues/38682#issuecomment-1217402048

Comment:
Note the issue is kind of fun, because Void installs stuff as non-root, but mapped to root via userns, so the kernel doesn't give out its "you are root, so you're exempt from setuid wiping" thing.

And Meson's own testsuite didn't catch that, because our test for the setuid functionality working, didn't include a binary with a build rpath to be deleted.

  parent reply	other threads:[~2022-08-17  3:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  9:06 [ISSUE] " egrain
2022-08-16 19:25 ` CameronNemo
2022-08-16 19:35 ` egrain
2022-08-16 20:15 ` CameronNemo
2022-08-16 20:15 ` CameronNemo
2022-08-16 20:16 ` CameronNemo
2022-08-16 20:20 ` CameronNemo
2022-08-16 20:27 ` egrain
2022-08-16 20:32 ` CameronNemo
2022-08-16 20:35 ` egrain
2022-08-16 20:38 ` CameronNemo
2022-08-16 20:39 ` egrain
2022-08-17  0:44 ` eli-schwartz
2022-08-17  2:56 ` eli-schwartz
2022-08-17  3:01 ` eli-schwartz [this message]
2022-08-17  8:29 ` egrain
2022-08-17 14:31 ` [ISSUE] [CLOSED] " paper42

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=20220817030100.MwzcwQeSPDd0WEyTSH9FYYOMDr8EAIW7iK8G0d0AUVs@z \
    --to=eli-schwartz@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).