Originally reported to security@ as a 'security issue' but isn't really
a Security grade bug. Was emailed individually to me separately from
Salvatore in email.

Original report contents are as follows and was originally sent by
Gabriel Corona into security@
---

Hi,

nginx-snippets contains TLS configuration snippets based on Mozilla TLS
generator. However, while the version of NGINX present in Trixie supports
post quantum cryptography (X25519MLKEM768), these configuration snippets
disable them with this line:

ssl_ecdh_curve X25519:prime256v1:secp384r1;

This configuration reduces the security of the TLS configuration and makes
the hosted applications/sites vulnerable to a potential "Harvest Now Decrypt
Later" attack.

The version in testing/unstable is not affected as it uses:

ssl_ecdh_curve ssl_ecdh_curve X25519MLKEM768:X25519:prime256v1:secp384r1;

---

This bug tracks this specific issue for changelogs.


Thomas

Hi,

This proposal does not meet the usual criteria. Whilst we can always make
exceptions, what's the justification in this case? It seems like a
suboptimal example config only.

Thanks,

Wrong bug, sorry.

After discussion with release / updates teams, this was rejected for
trixie-pu and will not land in Trixie's updates.

After discussion with the Security team, this does not warrant a
Security update.

As such, the only avenue to get this properly made available with
updated versions, etc. is via trixie-backports.

I do not have trixie-backports upload rights for this, and I believe
this would be NEW in trixie-backports. So I have something pending for
this in the Mentors process and will have an RFS filed for it to be
sponsored to trixie-backports.



Thomas