1 LoadModule ssl_module modules/mod_ssl.so
3 # This is the Apache server configuration file providing SSL support.
4 # It contains the configuration directives to instruct the server how to
5 # serve pages over an https connection. For detailing information about these
6 # directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
10 # Pseudo Random Number Generator (PRNG):
11 # Configure one or more sources to seed the PRNG of the SSL library.
12 # The seed data should be of good random quality.
13 # WARNING! On some platforms /dev/random blocks if not enough entropy
14 # is available. This means you then cannot use the /dev/random device
15 # because it would lead to very long connection times (as long as
16 # it requires to make more entropy available). But usually those
17 # platforms additionally provide a /dev/urandom device which doesn't
18 # block. So, if available, use this one instead. Read the mod_ssl User
19 # Manual for more details.
22 SSLRandomSeed startup file:/dev/urandom 256
23 SSLRandomSeed connect builtin
25 #SSLRandomSeed startup file:/dev/random 512
26 #SSLRandomSeed startup file:/dev/urandom 512
27 #SSLRandomSeed connect file:/dev/random 512
28 #SSLRandomSeed connect file:/dev/urandom 512
32 # When we also provide SSL we have to listen to the
33 # standard HTTP port (see above) and to the HTTPS port
35 # Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
36 # Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
43 ## All SSL configuration in this context applies both to
44 ## the main server and all SSL-enabled virtual hosts.
48 # Configure the pass phrase gathering process.
49 # The filtering dialog program (`builtin' is a internal
50 # terminal dialog) has to provide the pass phrase on stdout.
51 SSLPassPhraseDialog builtin
53 # Inter-Process Session Cache:
54 # Configure the SSL Session Cache: First the mechanism
55 # to use and second the expiring timeout (in seconds).
56 #SSLSessionCache dbm:/var/cache/httpd/ssl_scache
57 #SSLSessionCache shmcb:/var/run/ssl_scache(512000)
58 SSLSessionCache shmcb:/var/cache/httpd/ssl_scache(512000)
59 SSLSessionCacheTimeout 300
61 # FOLLOW SECURE DEFAULTS: https://wiki.mozilla.org/Security/Server_Side_TLS
63 # Usable SSL protocol flavors:
64 # This directive can be used to control the SSL protocol flavors mod_ssl
65 # should use when establishing its server environment. Clients then can only
66 # connect with one of the provided protocols.
67 SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
70 # List the ciphers that the client is permitted to negotiate.
71 # See the mod_ssl documentation for a complete list.
73 # High security: no weak ciphers, at least 256 bit
74 # (except TLS_AES_128_GCM_SHA256 which is required by TLSv1.3)
75 #SSLCipherSuite HIGH:!aNULL:!AES128:!ARIA128:!CAMELLIA128:!RSA:!SHA:!SHA256:!SHA384
77 # If you don't care about TLSv1.3 requirements and don't want any 128 bit
78 # cipher you can disable TLS_AES_128_GCM_SHA256 by uncommenting line below
79 #SSLCipherSuite TLSv1.3 TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384
81 # Strong security: no weak ciphers, at least 128 bit
82 # Recommended setting if you are not paranoid
83 SSLCipherSuite HIGH:!aNULL:!RSA:!SHA:!SHA256:!SHA384
85 # Medium security: includes some weak ciphers, at least 256 bit
86 # (except TLS_AES_128_GCM_SHA256 which is required by TLSv1.3)
87 #SSLCipherSuite HIGH:!aNULL:!AES128:!ARIA128:!CAMELLIA128:!RSA
89 # Low security: includes some weak ciphers, at least 128 bit
90 #SSLCipherSuite HIGH:!aNULL:!RSA
92 SSLHonorCipherOrder on
96 # Use this command to generate 4096 DH parameters (it will take long time):
97 # openssl dhparam -out /etc//httpd/ssl/dhparams.pem 4096
98 # When finished, uncomment line below
99 #SSLOpenSSLConfCmd DHParameters /etc/httpd/ssl/dhparams.pem
101 SSLOpenSSLConfCmd ECDHParameters secp384r1
102 SSLOpenSSLConfCmd Curves secp521r1:secp384r1
104 Header always set Strict-Transport-Security max-age=31556952;includeSubDomains
105 Header always set X-Frame-Options SAMEORIGIN
106 Header edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure
107 Header always set X-Content-Type-Options nosnif
111 SSLStaplingResponderTimeout 5
112 SSLStaplingReturnResponderErrors off
113 SSLStaplingCache shmcb:/var/cache/httpd/ocsp(128000)
115 # Whether to allow non-SNI clients to access a name-based virtual host.
116 #SSLStrictSNIVHostCheck on
119 ## SSL Virtual Host Context
122 <VirtualHost _default_:443>
124 # Enable/Disable SSL for this virtual host.
127 # Enable, if you have real ssl cert and want to cache OCSP
128 # https://www.digitalocean.com/community/tutorials/how-to-configure-ocsp-stapling-on-apache-and-nginx
131 # Server Certificate:
132 # Point SSLCertificateFile at a PEM encoded certificate. If
133 # the certificate is encrypted, then you will be prompted for a
134 # pass phrase. Note that a kill -HUP will prompt again. Keep
135 # in mind that if you have both an RSA and a DSA certificate you
136 # can configure both in parallel (to also allow the use of DSA
138 SSLCertificateFile /etc/httpd/ssl/server.crt
139 #SSLCertificateFile /etc/httpd/ssl/server-dsa.crt
141 # Server Private Key:
142 # If the key is not combined with the certificate, use this
143 # directive to point at the key file. Keep in mind that if
144 # you've both a RSA and a DSA private key you can configure
145 # both in parallel (to also allow the use of DSA ciphers, etc.)
146 SSLCertificateKeyFile /etc/httpd/ssl/server.key
147 #SSLCertificateKeyFile /etc/httpd/ssl/server-dsa.key
149 # Server Certificate Chain:
150 # Point SSLCertificateChainFile at a file containing the
151 # concatenation of PEM encoded CA certificates which form the
152 # certificate chain for the server certificate. Alternatively
153 # the referenced file can be the same as SSLCertificateFile
154 # when the CA certificates are directly appended to the server
155 # certificate for convinience.
156 #SSLCertificateChainFile /etc/httpd/ssl/ca.crt
158 # Certificate Authority (CA):
159 # Set the CA certificate verification path where to find CA
160 # certificates for client authentication or alternatively one
161 # huge file containing all of them (file must be PEM encoded)
162 # Note: Inside SSLCACertificatePath you need hash symlinks
163 # to point to the certificate files. Use the provided
164 # Makefile to update the hash symlinks after changes.
165 #SSLCACertificatePath /etc/httpd/ssl
166 #SSLCACertificateFile /etc/httpd/ssl/ca-bundle.crt
168 # Certificate Revocation Lists (CRL):
169 # Set the CA revocation path where to find CA CRLs for client
170 # authentication or alternatively one huge file containing all
171 # of them (file must be PEM encoded)
172 # Note: Inside SSLCARevocationPath you need hash symlinks
173 # to point to the certificate files. Use the provided
174 # Makefile to update the hash symlinks after changes.
175 #SSLCARevocationPath /etc/httpd/ssl
176 #SSLCARevocationFile /etc/httpd/ssl/ca-bundle.crl
178 # Client Authentication (Type):
179 # Client certificate verification type and depth. Types are
180 # none, optional, require and optional_no_ca. Depth is a
181 # number which specifies how deeply to verify the certificate
182 # issuer chain before deciding the certificate is not valid.
183 #SSLVerifyClient require
187 # With SSLRequire you can do per-directory access control based
188 # on arbitrary complex boolean expressions containing server
189 # variable checks and other lookup directives. The syntax is a
190 # mixture between C and Perl. See the mod_ssl documentation
193 #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
194 # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
195 # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
196 # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
197 # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
198 # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
201 # SSL Engine Options:
202 # Set various options for the SSL engine.
204 # Translate the client X.509 into a Basic Authorisation. This means that
205 # the standard Auth/DBMAuth methods can be used for access control. The
206 # user name is the `one line' version of the client's X.509 certificate.
207 # Note that no password is obtained from the user. Every entry in the user
208 # file needs this password: `xxj31ZMTZzkVA'.
210 # This exports two additional environment variables: SSL_CLIENT_CERT and
211 # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
212 # server (always existing) and the client (only existing when client
213 # authentication is used). This can be used to import the certificates
216 # This exports the standard SSL/TLS related `SSL_*' environment variables.
217 # Per default this exportation is switched off for performance reasons,
218 # because the extraction step is an expensive operation and is usually
219 # useless for serving static content. So one usually enables the
220 # exportation for CGI and SSI requests only.
222 # This denies access when "SSLRequireSSL" or "SSLRequire" applied even
223 # under a "Satisfy any" situation, i.e. when it applies access is denied
224 # and no other module can change it.
226 # This enables optimized SSL connection renegotiation handling when SSL
227 # directives are used in per-directory context.
228 #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
229 <FilesMatch "\.(cgi|shtml|phtml|php)$">
230 SSLOptions +StdEnvVars
232 <Directory "/home/services/httpd/cgi-bin">
233 SSLOptions +StdEnvVars
236 # SSL Protocol Adjustments:
237 # The safe and default but still SSL/TLS standard compliant shutdown
238 # approach is that mod_ssl sends the close notify alert but doesn't wait for
239 # the close notify alert from client. When you need a different shutdown
240 # approach you can use one of the following variables:
241 # o ssl-unclean-shutdown:
242 # This forces an unclean shutdown when the connection is closed, i.e. no
243 # SSL close notify alert is send or allowed to received. This violates
244 # the SSL/TLS standard but is needed for some brain-dead browsers. Use
245 # this when you receive I/O errors because of the standard approach where
246 # mod_ssl sends the close notify alert.
247 # o ssl-accurate-shutdown:
248 # This forces an accurate shutdown when the connection is closed, i.e. a
249 # SSL close notify alert is send and mod_ssl waits for the close notify
250 # alert of the client. This is 100% SSL/TLS standard compliant, but in
251 # practice often causes hanging connections with brain-dead browsers. Use
252 # this only for browsers where you know that their SSL implementation
254 # Notice: Most problems of broken clients are also related to the HTTP
255 # keep-alive facility, so you usually additionally want to disable
256 # keep-alive for those clients, too. Use variable "nokeepalive" for this.
257 # Similarly, one has to force some clients to use HTTP/1.0 to workaround
258 # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
259 # "force-response-1.0" for this.
260 <IfModule mod_setenvif.c>
261 BrowserMatch ".*MSIE [2-5]\..*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
262 BrowserMatch ".*MSIE [6-9]\..*" ssl-unclean-shutdown
265 # Per-Server Logging:
266 # The home of a custom SSL log file. Use this when you want a
267 # compact non-error SSL logfile on a virtual host basis.
268 #<IfModule mod_log_config.c>
269 # CustomLog logs/ssl_request_log "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
270 # # enable common log too, otherwise you be suprised of no access logs
271 # CustomLog logs/access_log common