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