3 Include sites-common/default
6 # Enable/Disable SSL for this virtual host.
9 # A self-signed (snakeoil) certificate can be created by installing
10 # the ssl-cert package. See
11 # /usr/share/doc/apache2.2-common/README.Debian.gz for more info.
12 # If both key and certificate are stored in the same file, only the
13 # SSLCertificateFile directive is needed.
14 SSLCertificateFile /etc/ssl/certs/general-web.crt
15 SSLCertificateKeyFile /etc/ssl/private/general-web.key
17 # Server Certificate Chain:
18 # Point SSLCertificateChainFile at a file containing the
19 # concatenation of PEM encoded CA certificates which form the
20 # certificate chain for the server certificate. Alternatively
21 # the referenced file can be the same as SSLCertificateFile
22 # when the CA certificates are directly appended to the server
23 # certificate for convinience.
24 #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt
26 # Certificate Authority (CA):
27 # Set the CA certificate verification path where to find CA
28 # certificates for client authentication or alternatively one
29 # huge file containing all of them (file must be PEM encoded)
30 # Note: Inside SSLCACertificatePath you need hash symlinks
31 # to point to the certificate files. Use the provided
32 # Makefile to update the hash symlinks after changes.
33 #SSLCACertificatePath /etc/ssl/certs/
34 #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt
36 # Certificate Revocation Lists (CRL):
37 # Set the CA revocation path where to find CA CRLs for client
38 # authentication or alternatively one huge file containing all
39 # of them (file must be PEM encoded)
40 # Note: Inside SSLCARevocationPath you need hash symlinks
41 # to point to the certificate files. Use the provided
42 # Makefile to update the hash symlinks after changes.
43 #SSLCARevocationPath /etc/apache2/ssl.crl/
44 #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
46 # Client Authentication (Type):
47 # Client certificate verification type and depth. Types are
48 # none, optional, require and optional_no_ca. Depth is a
49 # number which specifies how deeply to verify the certificate
50 # issuer chain before deciding the certificate is not valid.
51 #SSLVerifyClient require
55 # With SSLRequire you can do per-directory access control based
56 # on arbitrary complex boolean expressions containing server
57 # variable checks and other lookup directives. The syntax is a
58 # mixture between C and Perl. See the mod_ssl documentation
61 #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
62 # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
63 # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
64 # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
65 # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
66 # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
70 # Set various options for the SSL engine.
72 # Translate the client X.509 into a Basic Authorisation. This means that
73 # the standard Auth/DBMAuth methods can be used for access control. The
74 # user name is the `one line' version of the client's X.509 certificate.
75 # Note that no password is obtained from the user. Every entry in the user
76 # file needs this password: `xxj31ZMTZzkVA'.
78 # This exports two additional environment variables: SSL_CLIENT_CERT and
79 # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
80 # server (always existing) and the client (only existing when client
81 # authentication is used). This can be used to import the certificates
84 # This exports the standard SSL/TLS related `SSL_*' environment variables.
85 # Per default this exportation is switched off for performance reasons,
86 # because the extraction step is an expensive operation and is usually
87 # useless for serving static content. So one usually enables the
88 # exportation for CGI and SSI requests only.
90 # This denies access when "SSLRequireSSL" or "SSLRequire" applied even
91 # under a "Satisfy any" situation, i.e. when it applies access is denied
92 # and no other module can change it.
94 # This enables optimized SSL connection renegotiation handling when SSL
95 # directives are used in per-directory context.
96 #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
97 <FilesMatch "\.(cgi|shtml|phtml|php)$">
98 SSLOptions +StdEnvVars
100 <Directory /usr/lib/cgi-bin>
101 SSLOptions +StdEnvVars
104 # SSL Protocol Adjustments:
105 # The safe and default but still SSL/TLS standard compliant shutdown
106 # approach is that mod_ssl sends the close notify alert but doesn't wait for
107 # the close notify alert from client. When you need a different shutdown
108 # approach you can use one of the following variables:
109 # o ssl-unclean-shutdown:
110 # This forces an unclean shutdown when the connection is closed, i.e. no
111 # SSL close notify alert is send or allowed to received. This violates
112 # the SSL/TLS standard but is needed for some brain-dead browsers. Use
113 # this when you receive I/O errors because of the standard approach where
114 # mod_ssl sends the close notify alert.
115 # o ssl-accurate-shutdown:
116 # This forces an accurate shutdown when the connection is closed, i.e. a
117 # SSL close notify alert is send and mod_ssl waits for the close notify
118 # alert of the client. This is 100% SSL/TLS standard compliant, but in
119 # practice often causes hanging connections with brain-dead browsers. Use
120 # this only for browsers where you know that their SSL implementation
122 # Notice: Most problems of broken clients are also related to the HTTP
123 # keep-alive facility, so you usually additionally want to disable
124 # keep-alive for those clients, too. Use variable "nokeepalive" for this.
125 # Similarly, one has to force some clients to use HTTP/1.0 to workaround
126 # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
127 # "force-response-1.0" for this.
128 BrowserMatch ".*MSIE.*" \
129 nokeepalive ssl-unclean-shutdown \
130 downgrade-1.0 force-response-1.0