2
# This is the Apache server configuration file providing SSL support.
3
# It contains the configuration directives to instruct the server how to
4
# serve pages over an https connection. For detailing information about these
5
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
7
# Do NOT simply read the instructions in here without understanding
8
# what they do. They're here only as hints or reminders. If you are unsure
9
# consult the online docs. You have been warned.
13
# Pseudo Random Number Generator (PRNG):
14
# Configure one or more sources to seed the PRNG of the SSL library.
15
# The seed data should be of good random quality.
16
# WARNING! On some platforms /dev/random blocks if not enough entropy
17
# is available. This means you then cannot use the /dev/random device
18
# because it would lead to very long connection times (as long as
19
# it requires to make more entropy available). But usually those
20
# platforms additionally provide a /dev/urandom device which doesn't
21
# block. So, if available, use this one instead. Read the mod_ssl User
22
# Manual for more details.
24
#SSLRandomSeed startup file:/dev/random 512
25
#SSLRandomSeed startup file:/dev/urandom 512
26
#SSLRandomSeed connect file:/dev/random 512
27
#SSLRandomSeed connect file:/dev/urandom 512
31
# When we also provide SSL we have to listen to the
32
# standard HTTP port (see above) and to the HTTPS port
34
# Note: Configurations that use IPv6 but not IPv4-mapped addresses need two
35
# Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443"
42
## All SSL configuration in this context applies both to
43
## the main server and all SSL-enabled virtual hosts.
47
# Some MIME-types for downloading Certificates and CRLs
49
AddType application/x-x509-ca-cert .crt
50
AddType application/x-pkcs7-crl .crl
53
# Configure the pass phrase gathering process.
54
# The filtering dialog program (`builtin' is a internal
55
# terminal dialog) has to provide the pass phrase on stdout.
56
SSLPassPhraseDialog builtin
58
# Inter-Process Session Cache:
59
# Configure the SSL Session Cache: First the mechanism
60
# to use and second the expiring timeout (in seconds).
61
#SSLSessionCache dbm:@exp_runtimedir@/ssl_scache
62
SSLSessionCache shmcb:@exp_runtimedir@/ssl_scache(512000)
63
SSLSessionCacheTimeout 300
66
# Configure the path to the mutual exclusion semaphore the
67
# SSL engine uses internally for inter-process synchronization.
68
SSLMutex file:@exp_runtimedir@/ssl_mutex
71
## SSL Virtual Host Context
74
<VirtualHost _default_:443>
76
# General setup for the virtual host
77
DocumentRoot "@exp_htdocsdir@"
78
ServerName www.example.com:443
79
ServerAdmin you@example.com
80
ErrorLog @exp_logfiledir@/error_log
81
TransferLog @exp_logfiledir@/access_log
84
# Enable/Disable SSL for this virtual host.
88
# List the ciphers that the client is permitted to negotiate.
89
# See the mod_ssl documentation for a complete list.
90
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
93
# Point SSLCertificateFile at a PEM encoded certificate. If
94
# the certificate is encrypted, then you will be prompted for a
95
# pass phrase. Note that a kill -HUP will prompt again. Keep
96
# in mind that if you have both an RSA and a DSA certificate you
97
# can configure both in parallel (to also allow the use of DSA
99
SSLCertificateFile @exp_sysconfdir@/server.crt
100
#SSLCertificateFile @exp_sysconfdir@/server-dsa.crt
102
# Server Private Key:
103
# If the key is not combined with the certificate, use this
104
# directive to point at the key file. Keep in mind that if
105
# you've both a RSA and a DSA private key you can configure
106
# both in parallel (to also allow the use of DSA ciphers, etc.)
107
SSLCertificateKeyFile @exp_sysconfdir@/server.key
108
#SSLCertificateKeyFile @exp_sysconfdir@/server-dsa.key
110
# Server Certificate Chain:
111
# Point SSLCertificateChainFile at a file containing the
112
# concatenation of PEM encoded CA certificates which form the
113
# certificate chain for the server certificate. Alternatively
114
# the referenced file can be the same as SSLCertificateFile
115
# when the CA certificates are directly appended to the server
116
# certificate for convinience.
117
#SSLCertificateChainFile @exp_sysconfdir@/server-ca.crt
119
# Certificate Authority (CA):
120
# Set the CA certificate verification path where to find CA
121
# certificates for client authentication or alternatively one
122
# huge file containing all of them (file must be PEM encoded)
123
# Note: Inside SSLCACertificatePath you need hash symlinks
124
# to point to the certificate files. Use the provided
125
# Makefile to update the hash symlinks after changes.
126
#SSLCACertificatePath @exp_sysconfdir@/ssl.crt
127
#SSLCACertificateFile @exp_sysconfdir@/ssl.crt/ca-bundle.crt
129
# Certificate Revocation Lists (CRL):
130
# Set the CA revocation path where to find CA CRLs for client
131
# authentication or alternatively one huge file containing all
132
# of them (file must be PEM encoded)
133
# Note: Inside SSLCARevocationPath you need hash symlinks
134
# to point to the certificate files. Use the provided
135
# Makefile to update the hash symlinks after changes.
136
#SSLCARevocationPath @exp_sysconfdir@/ssl.crl
137
#SSLCARevocationFile @exp_sysconfdir@/ssl.crl/ca-bundle.crl
139
# Client Authentication (Type):
140
# Client certificate verification type and depth. Types are
141
# none, optional, require and optional_no_ca. Depth is a
142
# number which specifies how deeply to verify the certificate
143
# issuer chain before deciding the certificate is not valid.
144
#SSLVerifyClient require
148
# With SSLRequire you can do per-directory access control based
149
# on arbitrary complex boolean expressions containing server
150
# variable checks and other lookup directives. The syntax is a
151
# mixture between C and Perl. See the mod_ssl documentation
154
#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
155
# and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
156
# and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
157
# and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
158
# and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
159
# or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
162
# SSL Engine Options:
163
# Set various options for the SSL engine.
165
# Translate the client X.509 into a Basic Authorisation. This means that
166
# the standard Auth/DBMAuth methods can be used for access control. The
167
# user name is the `one line' version of the client's X.509 certificate.
168
# Note that no password is obtained from the user. Every entry in the user
169
# file needs this password: `xxj31ZMTZzkVA'.
171
# This exports two additional environment variables: SSL_CLIENT_CERT and
172
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
173
# server (always existing) and the client (only existing when client
174
# authentication is used). This can be used to import the certificates
177
# This exports the standard SSL/TLS related `SSL_*' environment variables.
178
# Per default this exportation is switched off for performance reasons,
179
# because the extraction step is an expensive operation and is usually
180
# useless for serving static content. So one usually enables the
181
# exportation for CGI and SSI requests only.
183
# This denies access when "SSLRequireSSL" or "SSLRequire" applied even
184
# under a "Satisfy any" situation, i.e. when it applies access is denied
185
# and no other module can change it.
187
# This enables optimized SSL connection renegotiation handling when SSL
188
# directives are used in per-directory context.
189
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
190
<FilesMatch "\.(cgi|shtml|phtml|php)$">
191
SSLOptions +StdEnvVars
193
<Directory "@exp_cgidir@">
194
SSLOptions +StdEnvVars
197
# SSL Protocol Adjustments:
198
# The safe and default but still SSL/TLS standard compliant shutdown
199
# approach is that mod_ssl sends the close notify alert but doesn't wait for
200
# the close notify alert from client. When you need a different shutdown
201
# approach you can use one of the following variables:
202
# o ssl-unclean-shutdown:
203
# This forces an unclean shutdown when the connection is closed, i.e. no
204
# SSL close notify alert is send or allowed to received. This violates
205
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
206
# this when you receive I/O errors because of the standard approach where
207
# mod_ssl sends the close notify alert.
208
# o ssl-accurate-shutdown:
209
# This forces an accurate shutdown when the connection is closed, i.e. a
210
# SSL close notify alert is send and mod_ssl waits for the close notify
211
# alert of the client. This is 100% SSL/TLS standard compliant, but in
212
# practice often causes hanging connections with brain-dead browsers. Use
213
# this only for browsers where you know that their SSL implementation
215
# Notice: Most problems of broken clients are also related to the HTTP
216
# keep-alive facility, so you usually additionally want to disable
217
# keep-alive for those clients, too. Use variable "nokeepalive" for this.
218
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
219
# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
220
# "force-response-1.0" for this.
221
BrowserMatch ".*MSIE.*" \
222
nokeepalive ssl-unclean-shutdown \
223
downgrade-1.0 force-response-1.0
225
# Per-Server Logging:
226
# The home of a custom SSL log file. Use this when you want a
227
# compact non-error SSL logfile on a virtual host basis.
228
CustomLog @exp_logfiledir@/ssl_request_log \
229
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"