From: "Vincenzo Palazzo" <vincenzopalazzodev@gmail.com>
To: "FUJITA Tomonori" <fujita.tomonori@gmail.com>,
<rust-for-linux@vger.kernel.org>
Subject: Re: Rust in-kernel TLS handshake
Date: Fri, 06 Jan 2023 10:57:08 +0100 [thread overview]
Message-ID: <CPL0NRGMD1WF.1FI5PCWZWOZ19@vincent> (raw)
In-Reply-To: <CAJ+Zx=3OwXeJNsz8DLp_94ciWpQKoiV75v=XH3FoUQKW==_S8w@mail.gmail.com>
This sounds pretty exciting, and I think to play with it a little
the bit will help to see what the future looks like, also this
seems a really good use case of rust in the Kernel.
Let me know if there is a need for help, I had some free time in
the next coming months.
Cheers!
Vincent.
On Wed Dec 28, 2022 at 2:33 AM CET, FUJITA Tomonori wrote:
> Hi,
>
> I've started in-kernel TLS handshake implementation in Rust.
> https://github.com/fujita/rust-tls
>
> There is some debate over in-kernel TLS handshake mainly because of
> the complexity. I'd like to see if Rust could help with auditing such
> complicated security-relevant code in the kernel.
>
> I worked on QUIC as a consumer of TLS. This can establish a QUIC connection
> with Quinn's example client, Rust QUIC implementation. Only minimum
> server side functionality and connection establishment are supported.
>
> From the perspective of Rust-for-Linux, the main work is implementing
> APIs for crypto subsystem. Also libraries such as working with buffers
> (like Tokio's bytes) would be helpful, I think (should be useful for
> other projects). I'll work for mainline. Meanwhile you can compile
> this kernel module
> with my fork.
>
> Opinions?
>
> Resend due to a delivery issue. Sorry if you got this twice.
prev parent reply other threads:[~2023-01-06 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 1:33 Rust in-kernel TLS handshake FUJITA Tomonori
2022-12-28 13:50 ` Alex Gaynor
2022-12-29 23:34 ` FUJITA Tomonori
2023-01-06 9:57 ` Vincenzo Palazzo [this message]
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=CPL0NRGMD1WF.1FI5PCWZWOZ19@vincent \
--to=vincenzopalazzodev@gmail.com \
--cc=fujita.tomonori@gmail.com \
--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