From: "Chuck Lever" <cel@kernel.org>
To: "Sagi Grimberg" <sagi@grimberg.me>,
"Chuck Lever" <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org, "Steve Dickson" <steved@redhat.com>
Subject: Re: [PATCH] nfs.man: Document mtls mount parameters cert_serial and privkey_serial
Date: Tue, 05 May 2026 18:09:08 +0200 [thread overview]
Message-ID: <f1a55c7d-6532-4738-b2ca-f2aea1b65d2d@app.fastmail.com> (raw)
In-Reply-To: <2934bfbb-c5df-423b-b246-f28da326d70a@grimberg.me>
On Tue, May 5, 2026, at 6:05 PM, Sagi Grimberg wrote:
> On 05/05/2026 17:26, Chuck Lever wrote:
>>
>> On Tue, May 5, 2026, at 4:20 PM, Sagi Grimberg wrote:
>>> Two new mount params for x.509 certificate and private key pair used
>>> for mTLS authentication. These have been added a while ago, document
>>> them officially.
>> NAK
>>
>> There is a very good reason they have not been added to nfs(5) already.
>> As I stated before, these are part of an internal kernel-user space API.
>> They are not intended to be user administrative controls.
>
> Ah ok, I guess I misunderstood the thread.
> So what do you think the user interface for this if not key serials?
I don’t have an answer for that question.
Again, I had no idea this capability was
a priority so I haven’t thought it through yet. When LSF is done I will give
it some thought.
--
Chuck Lever
prev parent reply other threads:[~2026-05-05 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 14:20 [PATCH] nfs.man: Document mtls mount parameters cert_serial and privkey_serial Sagi Grimberg
2026-05-05 14:26 ` Chuck Lever
2026-05-05 16:05 ` Sagi Grimberg
2026-05-05 16:09 ` Chuck Lever [this message]
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=f1a55c7d-6532-4738-b2ca-f2aea1b65d2d@app.fastmail.com \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=steved@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).