From: Chuck Lever III <chuck.lever@oracle.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Jeff Layton <jlayton@kernel.org>,
"kernel-tls-handshake@lists.linux.dev"
<kernel-tls-handshake@lists.linux.dev>
Subject: Re: problems getting rpc over tls to work
Date: Tue, 28 Mar 2023 14:47:25 +0000 [thread overview]
Message-ID: <F31CB471-2480-4E16-9840-E3D637B6E38E@oracle.com> (raw)
In-Reply-To: <CAN-5tyHLRkhn6wiEMf-JfbSWR-ovi9GZ4THvP9bmTJxTENc8iA@mail.gmail.com>
> On Mar 28, 2023, at 10:44 AM, Olga Kornievskaia <aglo@umich.edu> wrote:
>
> My next stumble which Chuck helped me was that negotiated cipher was
> ChaCha20Poly which I didn't have enabled in my kernel. So look that
> you have CONFIG_CRYPTO_CHACHA20POLY1305 compiled in the kernel.
Yeah, I think tlshd's ability to detect what is supported by the
local kernel is still not perfect. To that end I was thinking of
adding a configuration option to /etc/tlshd.conf to enable and
disable these algorithms.
Does anyone know if ChaCha and Poly1305 is going to be enabled
in present or future Fedora/OpenSuSE kernels?
--
Chuck Lever
next prev parent reply other threads:[~2023-03-28 14:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 12:27 problems getting rpc over tls to work Jeff Layton
2023-03-28 12:55 ` Jeff Layton
2023-03-28 14:04 ` Chuck Lever III
2023-03-28 14:23 ` Benjamin Coddington
2023-03-28 14:29 ` Jeff Layton
2023-03-28 14:39 ` Olga Kornievskaia
2023-03-28 14:45 ` Chuck Lever III
2023-03-28 14:50 ` Olga Kornievskaia
2023-03-28 15:06 ` Jeff Layton
2023-03-28 15:03 ` Jeff Layton
2023-03-28 15:05 ` Chuck Lever III
2023-03-28 15:15 ` Jeff Layton
2023-03-28 15:19 ` Olga Kornievskaia
2023-03-28 15:30 ` Olga Kornievskaia
2023-03-28 15:48 ` Chuck Lever III
2023-03-28 14:41 ` Chuck Lever III
2023-03-28 13:29 ` Chuck Lever III
2023-03-28 13:51 ` Jeff Layton
2023-03-28 13:55 ` Chuck Lever III
2023-03-28 14:13 ` Jeff Layton
2023-03-28 14:25 ` Olga Kornievskaia
2023-03-28 14:38 ` Jeff Layton
2023-03-28 14:44 ` Olga Kornievskaia
2023-03-28 14:47 ` Chuck Lever III [this message]
2023-03-28 15:48 ` Jeff Layton
2023-03-28 16:06 ` Chuck Lever III
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=F31CB471-2480-4E16-9840-E3D637B6E38E@oracle.com \
--to=chuck.lever@oracle.com \
--cc=aglo@umich.edu \
--cc=jlayton@kernel.org \
--cc=kernel-tls-handshake@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 NNTP newsgroup(s).