kernel-tls-handshake.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Damian Peckett <damian@pecke.tt>
To: "kernel-tls-handshake@lists.linux.dev"
	<kernel-tls-handshake@lists.linux.dev>
Subject: Implementation of tlshd in Go
Date: Sat, 2 Mar 2024 18:31:11 +0100 (CET)	[thread overview]
Message-ID: <1440495327.67118.1709400671916@office.mailbox.org> (raw)

Hi,

As part of an exercise in better understanding the kTLS subsystem I've recently re-implemented the kernel TLS handshake daemon in Go.

https://github.com/dpeckett/tlshd-go

Right now it's a very experimental proof of concept but it should be pretty trivial to implement the majority of missing features (eg. PSK and server handshakes).

I think the most interesting aspect for me is how we are plan on dealing with x509 certificates/keys as the asymmetric key type naturally doesn't support reads.

Best regards,
Damian Peckett

                 reply	other threads:[~2024-03-02 17:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1440495327.67118.1709400671916@office.mailbox.org \
    --to=damian@pecke.tt \
    --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).