From: Luis Chamberlain <mcgrof@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, kdevops@lists.linux.dev
Subject: Re: [PATCH kdevops] ktls: allow setting up hosts with tlshd
Date: Tue, 12 Dec 2023 22:11:33 -0800 [thread overview]
Message-ID: <ZXlLFSLJY5ovCBBS@bombadil.infradead.org> (raw)
In-Reply-To: <20231212-ktls-v1-1-acfba0d36f75@kernel.org>
On Tue, Dec 12, 2023 at 02:35:38PM -0500, Jeff Layton wrote:
> Add a new option to the post-install "goals" phase to configure tlshd
> for TLS handshake upcalls. This adds a new playbook to build a CA,
> generate certs for the hosts, and then configure tlshd to use them.
>
> Finally, it also adds a new NFS fstests option to test RPC over TLS
> (using xprtsec=mtls).
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
All looks good to me.
Luis
prev parent reply other threads:[~2023-12-13 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 19:35 [PATCH kdevops] ktls: allow setting up hosts with tlshd Jeff Layton
2023-12-12 19:43 ` Chuck Lever
2023-12-12 20:12 ` Jeff Layton
2023-12-13 6:11 ` Luis Chamberlain [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=ZXlLFSLJY5ovCBBS@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=kdevops@lists.linux.dev \
/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).