Hide Forgot
LEGACY crypto policy sets jdk.tls.ephemeralDHKeySize to 1023, which is invalid and would throw exception if it was actually used [1]. Also DH keySize < 1023 in jdk.tls.disabledAlgorithms property seems weird, if key size of 1023 does not make sense. (Is there reason for that?). Btw. RHEL-8 page about crypto says < 1024 are disabled [2]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1882168#c1 [2] https://access.redhat.com/articles/3642912
Also value of jdk.tls.ephemeralDHKeySize=0 in "EMPTY" would be invalid.
The 1023 value was used because there were historically some servers on the public web that actually had 1023 bit DH parameters. Other crypto libraries supported by crypto-policies accept this value. I believe we can change it now to 1024. The EMPTY policy is not that interesting, it is there just for internal testing purposes of the crypto-policies config generators, but we can also adjust the generator to not emit anything if the value is 0. As for the issue of the value not being applied, ideally someone who has knowledge of the java configuration should submit a PR to the upstream crypto-policies repository on gitlab fixing those issues.
(In reply to Tomas Mraz from comment #2) > The 1023 value was used because there were historically some servers on the > public web that actually had 1023 bit DH parameters. Other crypto libraries > supported by crypto-policies accept this value. I believe we can change it > now to 1024. > > The EMPTY policy is not that interesting, it is there just for internal > testing purposes of the crypto-policies config generators, but we can also > adjust the generator to not emit anything if the value is 0. > thank you for explanation > As for the issue of the value not being applied, ideally someone who has > knowledge of the java configuration should submit a PR to the upstream > crypto-policies repository on gitlab fixing those issues. I think this is something, that can only be fixed in openjdk package. [1] From what I know properties from crypto policy file end-up in security properties but this one should end up in System properties instead. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1702356
(In reply to Tomas Mraz from comment #2) > The 1023 value was used because there were historically some servers on the > public web that actually had 1023 bit DH parameters. Other crypto libraries > supported by crypto-policies accept this value. I believe we can change it > now to 1024. > > The EMPTY policy is not that interesting, it is there just for internal > testing purposes of the crypto-policies config generators, but we can also > adjust the generator to not emit anything if the value is 0. > > As for the issue of the value not being applied, ideally someone who has > knowledge of the java configuration should submit a PR to the upstream > crypto-policies repository on gitlab fixing those issues. We can add support for handling system properties, but we first need these to be separated in the crypto-policies package. See bug 1883312.