From: FUJITA Tomonori <tomo@exabit.dev>
To: rust-for-linux@vger.kernel.org, netdev@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: [PATCH 0/2] rust: networking and crypto abstractions
Date: Mon, 15 May 2023 04:34:27 +0000 [thread overview]
Message-ID: <010101881db036fb-2fb6981d-e0ef-4ad1-83c3-54d64b6d93b3-000000@us-west-2.amazonses.com> (raw)
This includes initial rust abstractions for networking and crypto.
I've been working on in-kernel TLS 1.3 handshake in Rust on the top of
this. Currently you can run simple TLS server code, which does a
handshake, sets up kTLS (Kernel TLS offload) to read and write some
bytes.
https://github.com/fujita/rust-tls
Seems that there are some potential users for in-kernel TLS 1.3
handshake (can be used for QUIC protocol too). Hopefully Rust could
help with auditing complicated security-relevant code in the kernel.
The TLS code isn't ready for reviewing yet but I like to push the
dependency for upstream. There might be other potential users for
networking and crypto abstractions.
The series should be cleanly applied to rust-next tree (ac9a786).
Note that this doesn't include all the dependency for the in-kernel
TLS handshake code. You can find at:
https://github.com/fujita/linux/tree/rust-tls
FUJITA Tomonori (2):
rust: add synchronous message digest support
rust: add socket support
rust/bindings/bindings_helper.h | 4 +
rust/helpers.c | 24 ++++++
rust/kernel/crypto.rs | 108 +++++++++++++++++++++++++
rust/kernel/lib.rs | 4 +
rust/kernel/net.rs | 174 ++++++++++++++++++++++++++++++++++++++++
5 files changed, 314 insertions(+)
reply other threads:[~2023-05-15 5:33 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=010101881db036fb-2fb6981d-e0ef-4ad1-83c3-54d64b6d93b3-000000@us-west-2.amazonses.com \
--to=tomo@exabit.dev \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
/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).