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