public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [patch v3] Allow for unpriviledged nested containers
Date: Wed, 17 Nov 2021 12:06:58 +0100	[thread overview]
Message-ID: <8735nv82i5.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <xnh7cd3tlw.fsf@greed.delorie.com> (DJ Delorie's message of "Mon,  15 Nov 2021 18:08:11 -0500")

* DJ Delorie:

> Subject: Allow for unpriviledged nested containers
>
> When running a "make check" in an untrusted podman container, we do
> not have priviledges to mount a new /proc.  Previously, we just failed
> to initialize the container and thus all test-container tests were
> "unsupported".  With this change, we bind mount the parent's /proc,
> which we have priviledges to do.  Note that MS_REC is needed as /proc
> typically has things mounted within it, and not mounting those would
> be a security hole[*].

I see a new test failure with this, elf/tst-pldd.  Happens with
kernel-5.14.17-301.fc35.x86_64, kernel-5.14.13-100.fc33.x86_64,
linux-image-5.10.0-9-amd64_5.10.70-1, as a non-root user.

Thanks,
Florian


  reply	other threads:[~2021-11-17 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 23:08 DJ Delorie
2021-11-17 11:06 ` Florian Weimer [this message]
2021-11-17 22:44   ` DJ Delorie
2021-11-18 11:35     ` Florian Weimer
2021-11-18 18:37       ` DJ Delorie
2021-11-18 19:47         ` Florian Weimer
2021-11-18 19:52           ` DJ Delorie
2021-11-18 19:55             ` Florian Weimer
2021-11-18 20:18               ` DJ Delorie
2021-11-18 20:20                 ` Florian Weimer
2021-11-18 20:25                   ` DJ Delorie

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=8735nv82i5.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).