diff options
| author | Chuck Lever <cel@kernel.org> | 2026-10-06 11:31:15 -0400 |
|---|---|---|
| committer | Anna Schumaker <anna.schumaker@hammerspace.com> | 2026-10-12 16:28:08 -0400 |
| commit | e27b84e076c1b623218ebe2887ca21c2c3217f5e (patch) | |
| tree | 099b4c1b68a65c8e86b9c32837d8c2bdd118db22 /tools/lib/python | |
| parent | 7856eb255ef9ea70a3a4f5764c8f1fcdb72b0896 (diff) | |
| download | linux-next-e27b84e076c1b623218ebe2887ca21c2c3217f5e.tar.gz linux-next-e27b84e076c1b623218ebe2887ca21c2c3217f5e.zip | |
NFS: name the namespace .nfs keyring in the x509 handshake
Keys on the per-namespace .nfs keyring need not grant user read
permission once tlshd possesses the keyring, but nothing tells tlshd
which keyring to possess. An xprtsec=mtls mount can present only keys
that tlshd's own credentials can read, and one namespace's keys are
not isolated from another's.
Record the serial number of the namespace's .nfs keyring in the
nfs_client's xprtsec parameters under the x509 policy, so tlshd
possesses that keyring when it reads the certificate and private
key.
Signed-off-by: Chuck Lever <cel@kernel.org>
Signed-off-by: Anna Schumaker <anna.schumaker@hammerspace.com>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
