netdev - How should NFS, SUNRPC interact with Network and User Namespaces?

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>] [day] [month] [year] [list]

Message-ID: <CAMp4zn9=fa71sJL0MGSfos9pvCturBhL+61SU9aG_-H=YSquHg@mail.gmail.com>
Date:   Fri, 29 Jun 2018 10:32:26 -0700
From:   Sargun Dhillon <sargun@...gun.me>
To:     linux-fsdevel@...r.kernel.org, netdev <netdev@...r.kernel.org>
Cc:     David Howells <dhowells@...hat.com>,
        "Eric W . Biederman" <ebiederm@...ssion.com>
Subject: How should NFS, SUNRPC interact with Network and User Namespaces?

Today, sunrpc lives in net/sunrpc. As far as I can tell, the primary
production consumer of it is NFS. The RPC clients have the concept of
being tied back to a network namespace. On the other hand, NFS has its
own superblock with its own user namespace.

When sunrpc convert kuids to UIDs to send over the wire, should it use
the user namespace of the network namespace that the RPC client is
associated with? This is required for auth_unix (UID based).
Alternatively, should the sunrpc RPC client use the user namespace
associated with the NFS superblock?