Hello,
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.
The strongswan Android app already supports ML-KEM and strongswan 6
server itself also does in principle, with a simple flag ( --enable-ml
enable Module-Lattice-based crypto (ML-KEM) plugin.
)
With client and server having the same algorithm suite configured, they
agree, but then:
charon: 14[IKE] negotiated key exchange method ML_KEM_768 not supported
Since the client sends the corresponding proposal, it looks very much
like the server lacks compiled-in support for ML-KEM.
Is there still a reason in 2026 not to include PQC support?
Greetings,
Stefan Winter
