2 ms·
When I setup TLS for web or smtp, there's an option to generate custom dh params. So basically one must generate new dh params for every installation to be safe
by vbezhenar 11y ago
When I setup TLS for web or smtp, there's an option to generate custom dh params. So basically one must generate new dh params for every installation to be safe against attack presented in the article, is it correct?
- schoen 11y agoThat would work, but there's still a problem when the client can't verify that the parameters are safe, at least when using client certificates. See the references in section 9.7 of https://datatracker.ietf.org/doc/draft-ietf-tls-negotiated-ff-dhe/ https://datatracker.ietf.org/doc/draft-ietf-tls-negotiated-f... As a result, that draft proposes using specific much larger parameters, on the basis of scaling considerations for the attacker. I think the authors of this paper endorse this solution. (It's OK in general if you share parameters with someone else, it just means that an attacker who can do this precomputation for those parameters gets to attack both of your DH sessions as a result.)
- Natanael_L 11y agoOnly if the parameters are too small (1024 bits and close), and if the source of the parameters aren't necessarily trustworthy (maybe because of lack of verification). 2048 bit parameters should be good enough.
- deleted 11y ago[deleted]