On Mon, 25 Aug 2025 18:18:01 GMT, Artur Barashev <abaras...@openjdk.org> wrote:
>> [JDK-8349583](https://bugs.openjdk.org/browse/JDK-8349583) implementation >> assumes that OpenJDK client always sends "signature_algorithms_cert" >> extension together with "signature_algorithms" extension. But we didn't >> account for `jdk.tls.client.disableExtensions` and >> `jdk.tls.server.disableExtensions` system properties which can disable >> producing "signature_algorithms_cert" extension. This is an issue similar to >> [JDK-8355779](https://bugs.openjdk.org/browse/JDK-8355779) but on the >> extension producing side. >> >> Per TLSv1.3 RFC: >> >>> If no "signature_algorithms_cert" extension is >>> present, then the "signature_algorithms" extension also applies to >>> signatures appearing in certificates. >> >> Also making a few cosmetic changes to the existing code. > > Artur Barashev has updated the pull request incrementally with two additional > commits since the last revision: > > - Update tests > - Revert "Include RSASSA-PKCS1-v1_5 and Legacy algorithms in > signature_algorithms for TLSv1.3" > > This reverts commit adc236be4bcac11614e2741c99545aa593f6af5b. Can a usecase be added for jdk.tls.server.disableExtensions if this option is being considered. ------------- PR Comment: https://git.openjdk.org/jdk/pull/26887#issuecomment-3222654920
