public inbox for containers@lists.linux.dev
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
	Linux Containers <containers@lists.linux-foundation.org>
Cc: Christian Brauner <christian.brauner@ubuntu.com>
Subject: Re: Use cases for multiple uid mapping?
Date: Sat, 29 Aug 2020 22:48:11 -0700	[thread overview]
Message-ID: <1598766491.5540.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <87zh6eiyv7.fsf@x220.int.ebiederm.org>

On Fri, 2020-08-28 at 10:17 -0500, Eric W. Biederman wrote:
[...]
> Can people follow up to this and report their use cases?
> 
> There are some real challenges and I would like to see if we
> can solve them, while avoiding scary problems like changing
> uids on write.

The main problem shiftfs has that fsuid doesn't is write at privileged
id, so mainly safely writing to kuid 0.

shiftfs tried to solve this by exposing the shifted mount point safely,
but maybe there's another way to do it.

James

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

  parent reply	other threads:[~2020-08-30  5:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 15:17 Use cases for multiple uid mapping? Eric W. Biederman
2020-08-28 15:55 ` Stéphane Graber via Containers
2020-08-28 17:03   ` Sargun Dhillon
2020-08-30  5:48 ` James Bottomley [this message]
2020-09-01  6:06 ` Serge E. Hallyn
2020-09-01 14:53   ` Eric W. Biederman
2020-09-24 17:09     ` Alban Crequy
2020-09-25  8:13       ` Christian Brauner

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=1598766491.5540.2.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    /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