<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p><br>
</p>
<p>I see the last update to this bug was in 2020. A lot of things
happened regarding PQC in that time, including the finalised
standardisation of ML-KEM.</p>
<p>The strongswan Android app already supports ML-KEM and strongswan
6 server itself also does in principle, with a simple flag ( <span
style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;"> --enable-ml
enable Module-Lattice-based crypto (ML-KEM)
plugin.</span><br>
<span style="color:#000000;background-color:#ffffff;"></span>)</span>
</p>
<p>With client and server having the same algorithm suite
configured, they agree, but then:</p>
<p>
<span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">charon:
14[IKE] negotiated key exchange method ML_KEM_768</span> not
supported<br>
</span><br>
</p>
<p>Since the client sends the corresponding proposal, it looks very
much like the server lacks compiled-in support for ML-KEM.</p>
<p>Is there still a reason in 2026 not to include PQC support?</p>
<p><br>
</p>
<p>Greetings,</p>
<p><br>
</p>
<p>Stefan Winter</p>
</body>
</html>