When OpenSSL 3.5.x will be integrated in order, for Kong, to be PQC safe for TLS/mTLS ?

[fco-code-org]

Hello everyone,

As far as I know, the latest Kong version (eg 3.9) integrates Nginx 1.25.3 and uses TLS library OpenSSL 3.2.3.
In order, for Kong, to be PQC safe, it has, at least, to integrate OpenSSL 3.5.x.

When OpenSSL 3.5.x will be integrated in next Kong releases ? Is there any roadmap on this topic ?

Best Regards.

[chronolaw]

Sorry, as far as I know that we have no clear planning about it.

[chronolaw]

I think that we could build kong with openssl 3.5 by ourself.

[sdickhoven]

judging by the existence of this file in the openresty repo, i assume that the latest versions of openresty already support openssl v3.5+.

i'm not sure how openresty / openssl is integrated into kong. but hopefully it won't be a big effort to pull in a pqc-capable version of openssl. 🤞

since quantum computers are not yet capable of breaking anything but "toy" examples of public key crypto, the main concern right now are "harvest now, decrypt later" attacks.

...and this is why it is important for everyone to start protecting the exchange of symmetric session keys as soon as possible.

symmetric encryption of data is not susceptible to quantum computer-aided cryptanalysis. but the keys used for this symmetric encryption are (currently) exchanged using pqc-vulnerable public key algorithms.

amazon, cloudflare, google, mozilla, etc. have all rolled out X25519MLKEM768 (which is a hybrid algorithm) for key exchange.

openssh has been using mlkem768x25519-sha256 (added 2025) and sntrup761x25519-sha512 (added 2022) for key exchange.

so, yeah, i would love to see kong pull in an openssl version that supports at least some of the new pqc algorithms. 😍