linux-kernel - Re: [PATCH v1 2/9] fs/fuse: add FUSE_OWNER_UID_GID

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJfpegtHQsEUuFq1k4ZbTD3E1h-GsrN3PWyv7X8cg6sfU_W2Yw@mail.gmail.com>
Date: Thu, 29 Aug 2024 20:58:55 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@...onical.com>
Cc: Christian Brauner <brauner@...nel.org>, mszeredi@...hat.com, stgraber@...raber.org, 
	linux-fsdevel@...r.kernel.org, Seth Forshee <sforshee@...nel.org>, 
	Amir Goldstein <amir73il@...il.com>, Bernd Schubert <bschubert@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/9] fs/fuse: add FUSE_OWNER_UID_GID_EXT extension

On Thu, 29 Aug 2024 at 19:41, Aleksandr Mikhalitsyn
<aleksandr.mikhalitsyn@...onical.com> wrote:

> Let's think about it a bit more and if you confirm that we want to go
> this way, then I'll rework my patches.

And ACK from Christian would be good.

I don't see why this would be a radical change: idmapping changes the
meaning of fsuid/fsgid, so we now can't send those to the server in
the non-create case.  The only thing that changes is that an "invalid
ID" value is introduced into the protocol.  Probably makes sense to
explicitly define this valiue in <uapi/linux/fuse.h>.

Thanks,
Miklos