mod_ssl In Depth: Certificates, Cipher Suites & OCSP Stapling

Web Servers Fundamentals Chapter 7 paired SSLEngine on with SSLCertificateFile/SSLCertificateKeyFile and deliberately stopped there — it assumes HTTPS/TLS Fundamentals already covers what a certificate or a TLS handshake actually is, and this chapter keeps that same assumption. What neither of those courses covered is the set of mod_ssl directives that actually determine how secure that connection really is: which TLS versions are even allowed, which ciphers get used, and how the client confirms the certificate hasn't been revoked without slowing every connection down.

SSLCertificateFile Can Now Hold the Full Chain

Since Apache 2.4.8, SSLCertificateFile accepts a single file containing the leaf certificate and the full intermediate chain, concatenated in order — the separate SSLCertificateChainFile directive Fundamentals never mentioned still works for older setups, but a modern config typically doesn't need it at all. This is exactly the kind of detail that changes across Apache versions and is easy to find outdated advice about.

SSLProtocol: Restricting Which TLS Versions Are Allowed

SSLProtocol controls which TLS (and legacy SSL) versions Apache will negotiate at all. The -all then +TLSv1.2 +TLSv1.3 pattern — deny everything, then explicitly re-allow only what's wanted — is the recommended form specifically because it fails safe: if a future TLS version is ever added to Apache's supported list by default, a config written this way doesn't silently start allowing it. A config that instead lists only positives (+TLSv1.2 +TLSv1.3 with no leading -all) can leave older, weaker protocol versions still enabled underneath, depending on Apache's own compiled-in defaults.

SSLCipherSuite & SSLHonorCipherOrder

SSLCipherSuite takes a colon-separated cipher string: HIGH selects strong ciphers as a starting set, and each !-prefixed entry explicitly excludes a specific weak option (aNULL — no authentication at all, MD5 and 3DES — both cryptographically weak by modern standards) that might otherwise sneak in under a broader category. SSLHonorCipherOrder on tells Apache to enforce its own preferred cipher order rather than deferring to whatever order the connecting client offers — mainly relevant for TLS 1.2 and earlier, since TLS 1.3 negotiates from a small, fixed, already-strong cipher list and doesn't need this kind of manual curation.

OCSP Stapling

OCSP (Online Certificate Status Protocol) is how a client checks whether a certificate has been revoked since issuance. Without stapling, that check is the client's own job: the browser itself contacts the certificate authority's OCSP responder on every connection — a real, live network round-trip that adds latency, can fail if the CA's responder is slow or unreachable, and quietly tells the CA which sites a given client is visiting. OCSP stapling moves that job to the server: Apache itself periodically fetches a signed, time-stamped "this certificate is still valid" response from the CA (cached and refreshed on its own schedule, not per-request), and attaches — staples — that response directly into the TLS handshake. The client gets the same proof of validity without ever contacting the CA itself.

Hands-On Exercises