Re:Socat: “the hard coded 1024 bit DH p parameter was not pr...
by agwa on Monday February 01, 2016 @02:07PM
(#11014395)
This is a vulnerability in socat's TLS support. It has nothing to do with OpenSSL (besides the fact that OpenSSL provided a footgun API by leaving it to application developers to supply DH parameters).
[ Parent
| on HN ]
Re:Socat: “the hard coded 1024 bit DH p parameter was not pr...
by ChuckMcM on Monday February 01, 2016 @02:12PM
(#11014440)
"Footgun API" - I like that!
Its an interesting challenge though, I wonder if the person who picked the constant the first time understood the ramifications of it being prime or not. And if they did, how hard they worked to validate its primality.
Re:Socat: “the hard coded 1024 bit DH p parameter was not pr...
by jaxb on Tuesday February 02, 2016 @02:06AM
(#11018010)
btw, they recommend checking custom params via DH_check() (https://wiki.openssl.org/index.php/Diffie-Hellman_parameters...) but, appparently, neither apache nor nginx do this...