From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: 戴维 <daiwei@sunkaisens.com>
Cc: buildroot <buildroot@buildroot.org>, "Jérôme Pouiller" <jezz@sysmic.org>
Subject: Re: [Buildroot] 回复: [PATCH 1/3] package/strongswan: enable kernel-libipsec
Date: Sun, 11 Oct 2026 09:25:03 +0200 [thread overview]
Message-ID: <ass5tH9_w2Ps5Hfa@windsurf> (raw)
In-Reply-To: <845128ba-bcca-4acc-97b7-658e7bdf9859.daiwei@sunkaisens.com>
Hello!
On Tue, Sep 29, 2026 at 05:01:29PM +0800, 戴维 wrote:
> Sorry for the late reply over the holiday. After checking the official docs, I
> believe Patch 1 should be reverted and kept out of master for now. StrongSwan
> explicitly notes:
>
> libipsec is not intended for scenarios with high amounts of traffic or high
> burst traffic. It is not optimized for performance and buffers each packet in
> memory.
> In combination with insufficient processor power this will lead to a out of
> memory condition and a crash of charon or the whole device.
> SA and policy lookups are also not particularly optimized.
>
> I primarily use this plugin to prevent installing SAs into the kernel IPsec
> stack. In standard XFRM,
> sensitive state materials like K and XRES stored in the kernel SPD/SAD can be
> read in real time (e.g., via ip xfrm),
> introducing major security risks for traffic decryption. Still, given official
> warnings about OOM risks and poor performance,
> we should wait for this feature to stabilize before adding it to master.
Thanks for the feedback. Based on this feedback, I've marked the patch
as Rejected in our patch tracking system.
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-11 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 7:40 [Buildroot] [PATCH 1/3] package/strongswan: enable kernel-libipsec Wei Dai
2026-09-20 7:40 ` [Buildroot] [PATCH 2/3] package/strongswan: add eap-aka-3gpp support Wei Dai
2026-09-20 12:24 ` Thomas Petazzoni via buildroot
2026-09-20 7:40 ` [Buildroot] [PATCH 3/3] package/strongswan: add systemd support Wei Dai
2026-09-20 12:24 ` Thomas Petazzoni via buildroot
2026-09-20 12:26 ` [Buildroot] [PATCH 1/3] package/strongswan: enable kernel-libipsec Thomas Petazzoni via buildroot
2026-09-29 7:21 ` Thomas Petazzoni via buildroot
2026-09-29 9:01 ` [Buildroot] 回复: " 戴维
2026-10-11 7:25 ` Thomas Petazzoni via buildroot [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=ass5tH9_w2Ps5Hfa@windsurf \
--to=buildroot@buildroot.org \
--cc=daiwei@sunkaisens.com \
--cc=jezz@sysmic.org \
--cc=thomas.petazzoni@bootlin.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