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