Recently, a new vulnerability in Diffie-Hellman, informally referred to as 'logjam' has been published, for which this page has been put together suggesting how to counter the vulnerability:

We have three recommendations for correctly deploying Diffie-Hellman for TLS:

  1. Disable Export Cipher Suites. Even though modern browsers no longer support export suites, the FREAK and Logjam attacks allow a man-in-the-middle attacker to trick browsers into using export-grade cryptography, after which the TLS connection can be decrypted. Export ciphers are a remnant of 1990s-era policy that prevented strong cryptographic protocols from being exported from United States. No modern clients rely on export suites and there is little downside in disabling them.
  2. Deploy (Ephemeral) Elliptic-Curve Diffie-Hellman (ECDHE). Elliptic-Curve Diffie-Hellman (ECDH) key exchange avoids all known feasible cryptanalytic attacks, and modern web browsers now prefer ECDHE over the original, finite field, Diffie-Hellman. The discrete log algorithms we used to attack standard Diffie-Hellman groups do not gain as strong of an advantage from precomputation, and individual servers do not need to generate unique elliptic curves.
  3. Generate a Strong, Unique Diffie Hellman Group. A few fixed groups are used by millions of servers, which makes them an optimal target for precomputation, and potential eavesdropping. Administrators should generate unique, 2048-bit or stronger Diffie-Hellman groups using "safe" primes for each website or server.

What are the best-practice steps I should take to secure my server as per the above recommendations?


3 Answers 3


From the article you linked, there are three recommended steps to protect yourself against this vulnerability. In principle these steps apply to any software you may use with SSL/TLS but here we will deal with the specific steps to apply them to Apache (httpd) since that is the software in question.

  1. Disable Export Cipher Suites

Dealt with in the configuration changes we'll make in 2. below (!EXPORT near the end of the SSLCipherSuite line is how we'll disable export cipher suites)

  1. Deploy (Ephemeral) Elliptic-Curve Diffie-Hellman (ECDHE)

For this, you need to edit a few settings in your Apache config files - namely SSLProtocol, SSLCipherSuite, SSLHonorCipherOrder to have a "best-practices" setup. Something like the following will suffice:

SSLProtocol             all -SSLv2 -SSLv3


SSLHonorCipherOrder     on

Note: as for which SSLCipherSuite setting to use, this is always changing, and it is a good idea to consult resources such as this one to check for the latest recommended configuration.

3. Generate a Strong, Unique Diffie Hellman Group

To do so, you can run

openssl dhparam -out dhparams.pem 2048.

Note that this will put significant load on the server whilst the params are generated - you can always get around this potential issue by generating the params on another machine and using scp or similar to transfer them onto the server in question for use.

To use these newly-generated dhparams in Apache, from the Apache Documentation:

To generate custom DH parameters, use the openssl dhparam command. Alternatively, you can append the following standard 1024-bit DH parameters from RFC 2409, section 6.2 to the respective SSLCertificateFile file:

(emphasis mine)

which is then followed by a standard 1024-bit DH parameter. From this we can infer that the custom-generated DH parameters may simply be appended to the relevant SSLCertificateFile in question.

To do so, run something similar to the following:

cat /path/to/custom/dhparam >> /path/to/sslcertfile

Alternatively, as per the Apache subsection of the article you originally linked, you may also specify the custom dhparams file you have created if you prefer not to alter the certificate file itself, thusly:

SSLOpenSSLConfCmd DHParameters "/path/to/dhparams.pem"

in whichever Apache config(s) are relevant to your particular SSL/TLS implementation - generally in conf.d/ssl.confor conf.d/vhosts.conf but this will differ depending on how you have configured Apache.

It is worth noting that, as per this link,

Before Apache 2.4.7, the DH parameter is always set to 1024 bits and is not user configurable. This has been fixed in mod_ssl 2.4.7 that Red Hat has backported into their RHEL 6 Apache 2.2 distribution with httpd-2.2.15-32.el6

On Debian Wheezy upgrade apache2 to 2.2.22-13+deb7u4 or later and openssl to 1.0.1e-2+deb7u17. The above SSLCipherSuite does not work perfectly, instead use the following as per this blog:


You should check whether your Apache version is later than these version numbers depending on your distribution, and if not - update it if at all possible.

Once you have performed the above steps to update your configuration, and restarted the Apache service to apply the changes, you should check that the configuration is as-desired by running the tests on SSLLabs and on the article related to this particular vulnerability.

  • 1
    As for the load put on the server by generating the params, you can always generate them on another machine and the simply scp or even copy-paste the file to the target server. There's no need to generate the params in production server.
    – Erathiel
    May 20, 2015 at 11:26
  • 2
    After you've changed your configuration, you may want to run a check at SSLLabs.com as well just to be sure. May 20, 2015 at 12:58
  • 2
    Is there a way to fix this vulnerability in Apache/2.2.22 (Ubuntu 12.04)? I appended dhparams.pem to certificate.crt but weakdh.org/sysadmin.html still complains
    – tersmitten
    May 20, 2015 at 14:59
  • 2
    @tersmitten That's a completely separate question to this one. May 20, 2015 at 16:26
  • 3
    you can allways run key generation by 'nice' command. so, you can put it as: nice 19 openssl dhparam -out dhparams.pem 2048 . This will work longer, but will consume only unused cpu time.
    – Znik
    Jun 9, 2015 at 9:25

Based on a patch of Winni Neessen I've published a fix for Apache/2.2.22 (Debian Wheezy, maybe also usable on Ubuntu): https://flo.sh/debian-wheezy-apache2-logjam-fix/ - thx. for your feedback.

  • 3
    this is more a hackish hack than a solution. putting a recent nginx infront of your apache as reverse-proxy would be far more easy, and one doesnt rely on a 3rd-party-apache. May 21, 2015 at 6:37
  • 6
    Why should we trust these binaries?
    – user
    May 21, 2015 at 12:23
  • 2
    You don't have to trust the binaries; you may recompile apache2.2.x yourself very easily following the steps explained if you take the time. This would furthermore increase your security, because then your setup has unique primary keys.
    – Flo
    May 23, 2015 at 0:05
  • Would suggest that people don't complain about patches fixing a problem in an opensource software. Jun 10, 2015 at 2:49
  • @FlorianHeigl I'm not even sure what to make of that comment...
    – BE77Y
    Jun 18, 2015 at 11:16

Instead of going the complex route of the above 'hacks', consider switching to nginx as your main webserver-software (not just caching or proxy). It obviously seems more up to current standards, security-wise, than the old apache-engines. By using the nginx repository it's giving you a way more up to date stable webserver-engine than apache.

I completely switched over. Saved me a lot of time-consuming problem-solving regarding TLS, and - for our configurations - it also freed up a lot of RAM in the same go. In fact, I found employment of nginx refreshingly simple and straightforward, compared to the myriad of config complications of httpd/apache I had grown accustomed to. Could be a matter of taste, I had become quite fluent in httpd/apache rewrite/config/maintenance before I turned, and it was easier than I feared it would be. There's appropriate recent info on nginx config available online, and its user-base is huge, very active and support-friendly. https://news.netcraft.com/wp-content/uploads/2018/11/wpid-wss-top-1m-share.png

  • 3
    nginx set up to allow for export ciphers would be exactly as vulnerable to the Logjam attack as an Apache server set up to allow for export ciphers. Also, the question asks for solutions in Apache.
    – user
    Nov 4, 2015 at 11:19
  • 2
    Actually, solution: either switch to a distribution that provides more up-to-date packages for software where you absolutely need a newer version (not just backported bug fixes, as is for example the case with Debian or CentOS), or build packages yourself from source (it's not hard) and install them using the package manager, or plain old install from source code (also not hard, but takes a little more work to manage). For a question that asks "how do I mitigate vulnerability X within Y software?", an answer that states "replace Y software with Z software" is often not a useful answer.
    – user
    Nov 4, 2015 at 14:36
  • 1
    Apache to Nginx isn't an upgrade, it's a replacement. Backporting is a possibility. If you have a lot of work invested in the Apache solution, completely throwing that out and replacing it with something else also takes a lot of work. And this question is still about solutions centered around Apache, not Nginx. I'm not going to spend more time arguing about this; when you post answers, make sure they answer the question as asked at the page top. If you want to post an answer encouraging people to switch from Apache to Nginx, by all means do so, but to a question that allows for Nginx.
    – user
    Nov 7, 2015 at 11:28
  • 1
    So properly configuring a software to be secure against known attacks is "a complex route of hacks"? I get A+ on ssllabs.com with a simple apache configuration, you just have to take your time and do some research to understand how to properly configure the software you're using, no hacks over here...
    – Chazy Chaz
    May 14, 2018 at 3:00
  • 2
    @Julius - the downvotes are likely more to do with the lack of value in your answer regarding the question asked, than any hidden "agenda" people apparently might have against nginx vs apache. As it happens, I exclusively use nginx due to my preference - but it was me who answered this question. "Switch to other software" is not an acceptable answer to "how to fix (any problem)". Not to mention, you also entirely missed the point of the actual vulnerability - it was in diffie-hellman key exchange, not apache (or nginx, or sshd, or...)
    – BE77Y
    Sep 4, 2018 at 14:33

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .