From: Jakub Kicinski <kuba@kernel.org>
To: Lauri Jakku <lja@lja.fi>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
rust-for-linux@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC] STCP: secure-by-default transport (kernel-level, experimental)
Date: Fri, 2 Jan 2026 15:49:57 -0800 [thread overview]
Message-ID: <20260102154957.69e86d64@kernel.org> (raw)
In-Reply-To: <aceecca9-61ae-454f-957f-875c740c0686@lja.fi>
On Mon, 22 Dec 2025 20:13:40 +0200 Lauri Jakku wrote:
> STCP is an experimental, TCP-like transport protocol that integrates
> encryption and authentication directly into the transport layer, instead
> of layering TLS on top of TCP.
>
> The motivation is not to replace TCP, TLS, or QUIC for general Internet
> traffic, but to explore whether *security-by-default at the transport
> layer* can simplify certain classes of systems—particularly embedded,
> industrial, and controlled environments—where TLS configuration,
> certificate management, and user-space complexity are a significant
> operational burden.
We tend to merge transport crypto protocol support upstream if:
- HW integration is needed; or
- some network filesystem/block device needs it.
Otherwise user space is a better place for the implementation.
next prev parent reply other threads:[~2026-01-02 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 15:24 [RFC] Secure TCP (STCP): Rust-based encrypted transport protocol for kernel integration Lauri Jakku, CEO Of Paxsudos IT
2025-11-10 23:55 ` Greg KH
2025-11-11 20:25 ` Miguel Ojeda
2025-11-12 4:04 ` Lauri Jakku, CEO Of Paxsudos IT
2025-12-22 13:31 ` Lauri Jakku, CEO Of Paxsudos IT
[not found] ` <c6cdc094-6714-437b-ba37-e3e62667f4aa@paxsudos.fi>
2025-12-22 18:13 ` [RFC] STCP: secure-by-default transport (kernel-level, experimental) Lauri Jakku
2026-01-02 23:49 ` Jakub Kicinski [this message]
2026-01-05 15:38 ` Lauri Jakku
2026-01-05 23:45 ` Jakub Kicinski
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=20260102154957.69e86d64@kernel.org \
--to=kuba@kernel.org \
--cc=lja@lja.fi \
--cc=miguel.ojeda.sandonis@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.