== It's time for me to stop using lighttpd There's another SSL configuration vulnerability going around; this one is called [[Logjam https://weakdh.org/]] ([[also https://blog.cloudflare.com/logjam-the-latest-tls-vulnerability-explained/]]). Part of the [[suggested fixes for it https://weakdh.org/sysadmin.html]] is to generate your own strong Diffie-Hellman group instead of using one of the default groups, and of course another fix is yet more SSL parameter fiddling. There have been quite a lot of SSL/TLS related issues lately, and many of them have required SSL parameter fiddling at least in the short term. I've had a [[long-standing flirtation with lighttpd ../sysadmin/PreparingHighLoadMirror]] and [[my personal site https://cks.mef.org/]] has used it since the start. But this latest SSL issue has crystallized something I've been feeling for a while, which is that [[lighttpd http://www.lighttpd.net/]] has not really been keeping up with the SSL times. Lighttpd cannot configure or de-configure a number of things that people want to; for example, it has no option to disable TLS v1.0 or SSL compression (although the latter is probably off in OpenSSL by now). OCSP stapling? You can forget it ([[from all appearances http://redmine.lighttpd.net/issues/2469]]). In general, the last release of lighttpd 1.4.x was a year ago, which is an eternity in SSL best practices land. For a while now I've been telling people when they asked me that I couldn't recommend lighttpd for new deployments if they cared about SSL security at all. Since I care [[increasingly much NoMoreHTTPOnlySoftware]] about SSL myself, it's really time for me to follow my own advice and move away from lighttpd to something else ([[Apache is the most likely candidate ApacheLove]], despite [[practical annoyances in my environment ../linux/DebianRightApacheConfig]]). It'll be annoying, but in the long run it will be good for me. I'll have a SSL configuration that I have much more trust in and that is much better supported by common resources like [[Mozilla's SSL configuration generator https://mozilla.github.io/server-side-tls/ssl-config-generator/]] and [[configuration guidelines https://wiki.mozilla.org/Security/Server_Side_TLS]]. There's certainly a part of me that regrets this, since lighttpd is a neat little idea and Apache is kind of a hulking monstrosity. But in practice, what matters on the Internet is that [[unmaintained software decays ../tech/InternetSoftwareDecay]]. Lighttpd is in practice more or less unmaintained, while Apache is very well maintained (partly because so many people use it). (Initially I was going to write that dealing with Logjam would push me over the edge right away, but it turns out that the [[Logjam resources page https://weakdh.org/sysadmin.html]] actually has settings for lighttpd for once.)