mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: "James Bottomley" <James.Bottomley@hansenpartnership.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	lsf-pc@lists.linux-foundation.org,
	"Christian Brauner" <christian@brauner.io>,
	"Stéphane Graber" <stgraber@stgraber.org>
Subject: Re: [LSF TOPIC] beyond uidmapping, & towards a better security model
Date: Wed, 21 Feb 2024 01:22:55 +0000	[thread overview]
Message-ID: <ZdVQb9KoVqKJlsbD@casper.infradead.org> (raw)
In-Reply-To: <qlmv2hjwzgnkmtvjpyn6zdnnmja3a35tx4nh6ldl23tkzh5reb@r3dseusgs3x6>

On Tue, Feb 20, 2024 at 07:25:58PM -0500, Kent Overstreet wrote:
> But there's real advantages to getting rid of the string <-> integer
> identifier mapping and plumbing strings all the way through:
> 
>  - creating a new sub-user can be done with nothing more than the new
>    username version of setuid(); IOW, we can start a new named subuser
>    for e.g. firefox without mucking with _any_ system state or tables
> 
>  - sharing filesystems between machines is always a pita because
>    usernames might be the same but uids never are - let's kill that off,
>    please

I feel like we need a bit of a survey of filesystems to see what is
already supported and what are desirable properties.  Block filesystems
are one thing, but network filesystems have been dealing with crap like
this for decades.  I don't have a good handle on who supports what at
this point.

As far as usernames being the same ... well, maybe.  I've been willy,
mrw103, wilma (twice!), mawilc01 and probably a bunch of others I don't
remember.  I don't think we'll ever get away from having a mapping
between different naming authorities.

  parent reply	other threads:[~2024-02-21  1:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17 20:56 Kent Overstreet
2024-02-17 22:31 ` Matthew Wilcox
2024-02-17 22:54   ` Kent Overstreet
2024-02-19 14:26 ` James Bottomley
2024-02-21  0:25   ` Kent Overstreet
2024-02-21  0:56     ` Stéphane Graber
2024-02-21  1:01       ` Kent Overstreet
2024-02-21  1:22     ` Matthew Wilcox [this message]
2024-02-21  2:07       ` Kent Overstreet
2024-02-21  2:15       ` NeilBrown
2024-02-29  8:51         ` Shyam Prasad N
2024-02-21  3:53     ` James Bottomley
2024-02-21 23:01       ` Kent Overstreet
2024-02-22  0:33         ` James Bottomley
2024-02-22  3:37           ` Kent Overstreet
2024-02-22  8:45             ` James Bottomley
2024-02-22 11:53               ` Kent Overstreet

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=ZdVQb9KoVqKJlsbD@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=christian@brauner.io \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=stgraber@stgraber.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

all inboxes | Powered by JetHome®