From: Hannes Reinecke <hare@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: kernel-tls-handshake@lists.linux.dev, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/4] tls-handshake: server-side support
Date: Fri, 17 Feb 2023 12:31:41 +0100 [thread overview]
Message-ID: <20230217113145.18916-1-hare@suse.de> (raw)
Hi all,
here are my patches to get server-side for PSK up and
(well, not exactly) running.
Pretty trivial, really; just adding two more netlink
attributes (showing the power of netlink; I really like
this interface) and split server_hello() into two functions.
Based on v4 of the tls handshake netlink patches.
Hannes Reinecke (4):
tls-handshake: add 'timeout' netlink attribute
tls-handshake: add 'keyring' netlink attribute
net/tls_handshake: split tls_server_hello()
tls_handshake: add 'keyring' argument to server hello
include/net/tls.h | 18 +++++--
include/uapi/linux/handshake.h | 2 +
net/tls/tls_handshake.c | 97 ++++++++++++++++++++++++++++++----
3 files changed, 103 insertions(+), 14 deletions(-)
--
2.35.3
next reply other threads:[~2023-02-17 11:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 11:31 Hannes Reinecke [this message]
2023-02-17 11:31 ` [PATCH 1/4] tls-handshake: add 'timeout' netlink attribute Hannes Reinecke
2023-02-17 11:58 ` Chuck Lever III
2023-02-17 12:17 ` Hannes Reinecke
2023-02-17 12:26 ` Chuck Lever III
2023-02-17 12:36 ` Hannes Reinecke
2023-02-17 12:38 ` Chuck Lever III
2023-02-17 11:31 ` [PATCH 2/4] tls-handshake: add 'keyring' " Hannes Reinecke
2023-02-17 12:00 ` Chuck Lever III
2023-02-17 12:24 ` Hannes Reinecke
2023-02-17 12:32 ` Chuck Lever III
2023-02-17 12:48 ` Hannes Reinecke
2023-02-17 12:56 ` Chuck Lever III
2023-02-17 11:31 ` [PATCH 3/4] net/tls_handshake: split tls_server_hello() Hannes Reinecke
2023-02-17 11:31 ` [PATCH 4/4] tls_handshake: add 'keyring' argument to server hello Hannes Reinecke
2023-02-17 11:56 ` [PATCH 0/4] tls-handshake: server-side support 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=20230217113145.18916-1-hare@suse.de \
--to=hare@suse.de \
--cc=chuck.lever@oracle.com \
--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