netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com
Cc: netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev
Subject: [PATCH net-next v1 0/7] In-kernel support for the TLS Alert protocol
Date: Tue, 18 Jul 2023 14:58:51 -0400	[thread overview]
Message-ID: <168970659111.5330.9206348580241518146.stgit@oracle-102.nfsv4bat.org> (raw)

IMO the kernel doesn't need user space (ie, tlshd) to handle the TLS
Alert protocol. Instead, a set of small helper functions can be used
to handle sending and receiving TLS Alerts for in-kernel TLS
consumers.

---

Chuck Lever (7):
      net/tls: Move TLS protocol elements to a separate header
      net/tls: Add TLS Alert definitions
      net/handshake: Add API for sending TLS Closure alerts
      SUNRPC: Send TLS Closure alerts before closing a TCP socket
      net/handshake: Add helpers for parsing incoming TLS Alerts
      SUNRPC: Use new helpers to handle TLS Alerts
      net/handshake: Trace events for TLS Alert helpers


 include/net/handshake.h          |   5 +
 include/net/tls.h                |   5 +-
 include/net/tls_prot.h           |  68 +++++++++++++
 include/trace/events/handshake.h | 160 +++++++++++++++++++++++++++++++
 net/handshake/Makefile           |   2 +-
 net/handshake/alert.c            | 115 ++++++++++++++++++++++
 net/handshake/handshake.h        |   4 +
 net/handshake/tlshd.c            |  23 +++++
 net/handshake/trace.c            |   2 +
 net/sunrpc/svcsock.c             |  50 +++++-----
 net/sunrpc/xprtsock.c            |  45 +++++----
 11 files changed, 433 insertions(+), 46 deletions(-)
 create mode 100644 include/net/tls_prot.h
 create mode 100644 net/handshake/alert.c

--
Chuck Lever


             reply	other threads:[~2023-07-18 18:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 18:58 Chuck Lever [this message]
2023-07-18 18:59 ` [PATCH net-next v1 1/7] net/tls: Move TLS protocol elements to a separate header Chuck Lever
2023-07-18 18:59 ` [PATCH net-next v1 2/7] net/tls: Add TLS Alert definitions Chuck Lever
2023-07-19  7:40   ` Hannes Reinecke
2023-07-18 19:00 ` [PATCH net-next v1 3/7] net/handshake: Add API for sending TLS Closure alerts Chuck Lever
2023-07-19  7:47   ` Hannes Reinecke
2023-07-19 13:24     ` Chuck Lever III
2023-07-18 19:00 ` [PATCH net-next v1 4/7] SUNRPC: Send TLS Closure alerts before closing a TCP socket Chuck Lever
2023-07-18 19:00 ` [PATCH net-next v1 5/7] net/handshake: Add helpers for parsing incoming TLS Alerts Chuck Lever
2023-07-19  7:52   ` Hannes Reinecke
2023-07-19 13:36     ` Chuck Lever III
2023-07-20  5:44       ` Hannes Reinecke
2023-07-20 14:22         ` Chuck Lever III
2023-07-18 19:01 ` [PATCH net-next v1 6/7] SUNRPC: Use new helpers to handle " Chuck Lever
2023-07-18 19:01 ` [PATCH net-next v1 7/7] net/handshake: Trace events for TLS Alert helpers Chuck Lever
2023-07-19  7:53   ` Hannes Reinecke

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=168970659111.5330.9206348580241518146.stgit@oracle-102.nfsv4bat.org \
    --to=cel@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel-tls-handshake@lists.linux.dev \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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 NNTP newsgroup(s).