Skip to content

Instantly share code, notes, and snippets.

@hroling
Last active July 29, 2025 11:38
Show Gist options
  • Select an option

  • Save hroling/85f36e86d48285f08161 to your computer and use it in GitHub Desktop.

Select an option

Save hroling/85f36e86d48285f08161 to your computer and use it in GitHub Desktop.
Apache 2.4 SSL config for A+ on SSLLabs.com
OLD stuff. This was not enough for an A+ anymore.
@ibrahim87

Copy link
Copy Markdown

very good

@angshumancn

Copy link
Copy Markdown

Does the above keyword support Apache/2.2.22 ?

@DarkLogicX

Copy link
Copy Markdown

Where is the "Default-SSL.conf" file?

Also when I put "SSLStaplingCache shmcb:/tmp/stapling_cache(128000)" in the SSL.conf file (the one in Httpd/conf.d/) httpd wouldn't start.

@cofifield

Copy link
Copy Markdown

Great Info

@zachariahtimothy

Copy link
Copy Markdown

Just used this, thanks for sharing! I omitted the public key pins and still received A+.

@cristiroma

Copy link
Copy Markdown

I'm not entirely sure below is correct, but using suggested config SSLProtocol -ALL -SSLv3 +TLSv1 +TLSv1.1 +TLSv1.2 - triggers https://www.whynopadlock.com/ to show warning that TLSv1 is enabled - which is not good. We are using SSLProtocol TLSv1.2 which is the current standard with upcoming TLSv1.3.

@RavSS

RavSS commented Jun 30, 2018

Copy link
Copy Markdown

I would avoid configuring HPKP which is the Header set Public-Key-Pins... line, it's depreciated and can cause serious downtime if you fail to use it correctly, like if you don't have backup certificates. E.g. Chrome 67 (and Google altogether) recently dropped support for it, and the end user has to enable it manually via Chrome flags. TLSv1 still might be required if you need to support older browsers and devices like IE10 and Android 4.3 or below versions.

@emilas44

Copy link
Copy Markdown

This does not give A+ anymore!

@hroling

hroling commented Jul 29, 2019

Copy link
Copy Markdown
Author

This does not give A+ anymore!

True. I will delete this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment