From: Jakub Kicinski <kuba@kernel.org>
To: Paul Wouters <paul@nohats.ca>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Steffen Klassert <steffen.klassert@secunet.com>,
netdev@vger.kernel.org, pabeni@redhat.com, borisp@nvidia.com,
gal@nvidia.com, cratiu@nvidia.com, rrameshbabu@nvidia.com,
tariqt@nvidia.com
Subject: Re: [RFC net-next 00/15] add basic PSP encryption for TCP connections
Date: Tue, 28 May 2024 11:09:24 -0700 [thread overview]
Message-ID: <20240528110924.0f131264@kernel.org> (raw)
In-Reply-To: <81646030-00b9-10ad-abed-a7a78f0c511e@nohats.ca>
On Tue, 28 May 2024 11:33:33 -0400 (EDT) Paul Wouters wrote:
> > It makes sense to work to get to an IETF standard protocol that
> > captures the same benefits. But that is independent from enabling what
> > is already implemented.
>
> How many different packet encryption methods should the linux kernel
> have? There are good reasons to go through standard bodies. Doing your
> own thing and then saying "but we did it already" to me does not feel
> like a strong argument. That's how we got wireguard with all of its
> issues of being written for a single use case, and now being unfit for
> generic use cases.
Now you made me curious. What's wrong with wireguard?
I have only heard good things.
next prev parent reply other threads:[~2024-05-28 18:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 12:56 [RFC net-next 00/15] add basic PSP encryption for TCP connections Paul Wouters
2024-05-22 13:03 ` Boris Pismenny
2024-05-28 9:42 ` Steffen Klassert
2024-05-28 13:49 ` Willem de Bruijn
2024-05-28 15:33 ` Paul Wouters
2024-05-28 18:09 ` Jakub Kicinski [this message]
2024-05-28 18:11 ` Willem de Bruijn
2024-05-31 6:09 ` Steffen Klassert
2024-05-31 14:46 ` Willem de Bruijn
-- strict thread matches above, loose matches on Subject: below --
2024-06-18 23:54 Singhai, Anjali
2024-06-19 8:39 ` Willem de Bruijn
2024-06-19 8:47 ` Willem de Bruijn
2024-06-20 21:32 ` Singhai, Anjali
2024-06-21 12:05 ` Willem de Bruijn
2024-06-22 0:30 ` Jakub Kicinski
2024-06-25 22:05 ` Singhai, Anjali
2024-06-25 23:17 ` Jakub Kicinski
2024-05-10 3:04 Jakub Kicinski
2024-05-29 9:16 ` Boris Pismenny
2024-05-29 18:50 ` Jakub Kicinski
2024-05-29 20:01 ` Boris Pismenny
2024-05-29 20:38 ` 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=20240528110924.0f131264@kernel.org \
--to=kuba@kernel.org \
--cc=borisp@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=gal@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@nohats.ca \
--cc=rrameshbabu@nvidia.com \
--cc=steffen.klassert@secunet.com \
--cc=tariqt@nvidia.com \
--cc=willemdebruijn.kernel@gmail.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).