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/cache/httpd/ssl_scache(512000)
59 # Replace this with one of the above (addition apache-mod_socache
60 # needs to be installed and a apropriate module has to be loaded)
61 SSLSessionCache nonenotnull
62 SSLSessionCacheTimeout 300
64 # Usable SSL protocol flavors:
65 # This directive can be used to control the SSL protocol flavors mod_ssl
66 # should use when establishing its server environment. Clients then can only
67 # connect with one of the provided protocols.
68 SSLProtocol all -SSLv2
71 # List the ciphers that the client is permitted to negotiate.
72 # See the mod_ssl documentation for a complete list.
73 SSLCipherSuite ALL:!ADH:!EXP:!LOW:!SSLv2:RC4+RSA:+HIGH:+MEDIUM
77 ## SSL Virtual Host Context
80 <VirtualHost _default_:443>
82 # Enable/Disable SSL for this virtual host.
86 # Point SSLCertificateFile at a PEM encoded certificate. If
87 # the certificate is encrypted, then you will be prompted for a
88 # pass phrase. Note that a kill -HUP will prompt again. Keep
89 # in mind that if you have both an RSA and a DSA certificate you
90 # can configure both in parallel (to also allow the use of DSA
92 SSLCertificateFile /etc/httpd/ssl/server.crt
93 #SSLCertificateFile /etc/httpd/ssl/server-dsa.crt
96 # If the key is not combined with the certificate, use this
97 # directive to point at the key file. Keep in mind that if
98 # you've both a RSA and a DSA private key you can configure
99 # both in parallel (to also allow the use of DSA ciphers, etc.)
100 SSLCertificateKeyFile /etc/httpd/ssl/server.key
101 #SSLCertificateKeyFile /etc/httpd/ssl/server-dsa.key
103 # Server Certificate Chain:
104 # Point SSLCertificateChainFile at a file containing the
105 # concatenation of PEM encoded CA certificates which form the
106 # certificate chain for the server certificate. Alternatively
107 # the referenced file can be the same as SSLCertificateFile
108 # when the CA certificates are directly appended to the server
109 # certificate for convinience.
110 #SSLCertificateChainFile /etc/httpd/ssl/ca.crt
112 # Certificate Authority (CA):
113 # Set the CA certificate verification path where to find CA
114 # certificates for client authentication or alternatively one
115 # huge file containing all of them (file must be PEM encoded)
116 # Note: Inside SSLCACertificatePath you need hash symlinks
117 # to point to the certificate files. Use the provided
118 # Makefile to update the hash symlinks after changes.
119 #SSLCACertificatePath /etc/httpd/ssl
120 #SSLCACertificateFile /etc/httpd/ssl/ca-bundle.crt
122 # Certificate Revocation Lists (CRL):
123 # Set the CA revocation path where to find CA CRLs for client
124 # authentication or alternatively one huge file containing all
125 # of them (file must be PEM encoded)
126 # Note: Inside SSLCARevocationPath you need hash symlinks
127 # to point to the certificate files. Use the provided
128 # Makefile to update the hash symlinks after changes.
129 #SSLCARevocationPath /etc/httpd/ssl
130 #SSLCARevocationFile /etc/httpd/ssl/ca-bundle.crl
132 # Client Authentication (Type):
133 # Client certificate verification type and depth. Types are
134 # none, optional, require and optional_no_ca. Depth is a
135 # number which specifies how deeply to verify the certificate
136 # issuer chain before deciding the certificate is not valid.
137 #SSLVerifyClient require
141 # With SSLRequire you can do per-directory access control based
142 # on arbitrary complex boolean expressions containing server
143 # variable checks and other lookup directives. The syntax is a
144 # mixture between C and Perl. See the mod_ssl documentation
147 #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
148 # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
149 # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
150 # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
151 # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
152 # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
155 # SSL Engine Options:
156 # Set various options for the SSL engine.
158 # Translate the client X.509 into a Basic Authorisation. This means that
159 # the standard Auth/DBMAuth methods can be used for access control. The
160 # user name is the `one line' version of the client's X.509 certificate.
161 # Note that no password is obtained from the user. Every entry in the user
162 # file needs this password: `xxj31ZMTZzkVA'.
164 # This exports two additional environment variables: SSL_CLIENT_CERT and
165 # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
166 # server (always existing) and the client (only existing when client
167 # authentication is used). This can be used to import the certificates
170 # This exports the standard SSL/TLS related `SSL_*' environment variables.
171 # Per default this exportation is switched off for performance reasons,
172 # because the extraction step is an expensive operation and is usually
173 # useless for serving static content. So one usually enables the
174 # exportation for CGI and SSI requests only.
176 # This denies access when "SSLRequireSSL" or "SSLRequire" applied even
177 # under a "Satisfy any" situation, i.e. when it applies access is denied
178 # and no other module can change it.
180 # This enables optimized SSL connection renegotiation handling when SSL
181 # directives are used in per-directory context.
182 #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
183 <FilesMatch "\.(cgi|shtml|phtml|php)$">
184 SSLOptions +StdEnvVars
186 <Directory "/home/services/httpd/cgi-bin">
187 SSLOptions +StdEnvVars
190 # SSL Protocol Adjustments:
191 # The safe and default but still SSL/TLS standard compliant shutdown
192 # approach is that mod_ssl sends the close notify alert but doesn't wait for
193 # the close notify alert from client. When you need a different shutdown
194 # approach you can use one of the following variables:
195 # o ssl-unclean-shutdown:
196 # This forces an unclean shutdown when the connection is closed, i.e. no
197 # SSL close notify alert is send or allowed to received. This violates
198 # the SSL/TLS standard but is needed for some brain-dead browsers. Use
199 # this when you receive I/O errors because of the standard approach where
200 # mod_ssl sends the close notify alert.
201 # o ssl-accurate-shutdown:
202 # This forces an accurate shutdown when the connection is closed, i.e. a
203 # SSL close notify alert is send and mod_ssl waits for the close notify
204 # alert of the client. This is 100% SSL/TLS standard compliant, but in
205 # practice often causes hanging connections with brain-dead browsers. Use
206 # this only for browsers where you know that their SSL implementation
208 # Notice: Most problems of broken clients are also related to the HTTP
209 # keep-alive facility, so you usually additionally want to disable
210 # keep-alive for those clients, too. Use variable "nokeepalive" for this.
211 # Similarly, one has to force some clients to use HTTP/1.0 to workaround
212 # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
213 # "force-response-1.0" for this.
214 <IfModule mod_setenvif.c>
215 BrowserMatch ".*MSIE.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
218 # Per-Server Logging:
219 # The home of a custom SSL log file. Use this when you want a
220 # compact non-error SSL logfile on a virtual host basis.
221 #<IfModule mod_log_config.c>
222 # CustomLog logs/ssl_request_log "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
223 # # enable common log too, otherwise you be suprised of no access logs
224 # CustomLog logs/access_log common