1

When setting up a web server with TLS support I've generated my dhparams with openssl dhparam -C 2048 some.pem. I understand that the output in some.pem are the parameters by which DH key exchange will be done and that they are by nature public values. With empirical testing it seems that I can rotate the dh parameters without clients programs complaining, but a few questions arise that I can't find answers to.

  • If I rotate the parameters with some cadence is there any benefit to doing so?
  • Is there any downside to rotation? ie could an attacker more easily masquerade as my web server?

Naively it seems that rotation of parameters would marginally increase security in the event that one particular set of parameters is compromised, but this seems unlikely. Does anyone have input on this?

  • If you use very popular parameters you run the risk of some massive organization precomputing results for it. Recomputing different parameters can take lots of CPU power and time on weaker hardware. – user Oct 9 at 17:32
  • @user, that sounds like it could be made into a good answer (where it can be voted on and earn you reputation). – Toby Speight Oct 9 at 18:13
  • @user that's a good point. In this case I am generating my own parameters, but I hadn't considered that popular parameters might be a target. – Darakian Oct 9 at 19:00
  • Mostly dupe security.stackexchange.com/questions/38206/… and security.stackexchange.com/questions/43355/… also note TLS1.3 no longer supports user-generated groups/parameters at all; if you still use DHE you must use the standardized rfc7917 groups, see rfc8446. PS Diffie with two 'i' – dave_thompson_085 Oct 10 at 4:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.