Enforce a minimum DH modulus size of 512 bits#9437
Enforce a minimum DH modulus size of 512 bits#9437bernd-edlinger wants to merge 1 commit intoopenssl:masterfrom
Conversation
[extended tests]
|
As this little exercise clearly shows: #9363 (comment) No doubt 512 is still too small, and needs to be raised in the near future. |
paulidale
left a comment
There was a problem hiding this comment.
Should a larger minimum be considered? 512 bits isn't a lot. Under $100 on EC2 several years ago.
|
Yeah, the question is what the minimum means - 1024 is probably still within the breakable limits for a three letter agency. And wouldn't it be better to just print a warning from the openssl application if generating anything below 2048 (or 1536 ?) bits that the parameters are breakable? |
|
I think at the TLS level we already enforce 1024 at our default security level of 1. |
|
Merged to master as 6de1fe9. Thanks! |
[extended tests] Reviewed-by: Paul Dale <[email protected]> (Merged from #9437)
|
Hmm, a very interesting thing happened in the CI build 26769.16 and 26849.16 In fact I can reproduce that, and it dead-locks for me: but not every seed exhibits this problem. |
|
Call stack for 1563830498: and 1563972976: |
The dh_test was failing because we now enforce a lower bound on the modulus size that may be used. A number of locations in dhtest.c were assuming that a very small modulus is valid. A 512 bit lower bound was introduced by PR openssl#9437 (commit 6de1fe9) and subsequently amended by PR openssl#9796 (commit feeb7ec). The CHANGES entry says this: * Enforce a minimum DH modulus size of 512 bits.
The dh_test was failing because we now enforce a lower bound on the modulus size that may be used. A number of locations in dhtest.c were assuming that a very small modulus is valid. A 512 bit lower bound was introduced by PR openssl#9437 (commit 6de1fe9) and subsequently amended by PR openssl#9796 (commit feeb7ec). The CHANGES entry says this: * Enforce a minimum DH modulus size of 512 bits.
Checklist