source: main/adopters/nm/trunk/src/main/serverconfigs/sas_server_dohr2simnmibis1/apache_httpd/extra/httpd-ssl.conf @ 25255

Last change on this file since 25255 was 25255, checked in by Paul Leo, 3 months ago

IBIS V3 Architecture
Updating Apache httpd SAS Server configs

File size: 13.5 KB
Line 
1#
2# This is the Apache server configuration file providing SSL support.
3# It contains the configuration directives to instruct the server how to
4# serve pages over an https connection. For detailed information about these
5# directives see <URL:http://httpd.apache.org/docs/2.4/mod/mod_ssl.html>
6#
7# Do NOT simply read the instructions in here without understanding
8# what they do.  They're here only as hints or reminders.  If you are unsure
9# consult the online docs. You have been warned. 
10#
11# Required modules: mod_log_config, mod_setenvif, mod_ssl,
12#          socache_shmcb_module (for default value of SSLSessionCache)
13
14#
15# Pseudo Random Number Generator (PRNG):
16# Configure one or more sources to seed the PRNG of the SSL library.
17# The seed data should be of good random quality.
18# WARNING! On some platforms /dev/random blocks if not enough entropy
19# is available. This means you then cannot use the /dev/random device
20# because it would lead to very long connection times (as long as
21# it requires to make more entropy available). But usually those
22# platforms additionally provide a /dev/urandom device which doesn't
23# block. So, if available, use this one instead. Read the mod_ssl User
24# Manual for more details.
25#
26#SSLRandomSeed startup file:/dev/random  512
27#SSLRandomSeed startup file:/dev/urandom 512
28#SSLRandomSeed connect file:/dev/random  512
29#SSLRandomSeed connect file:/dev/urandom 512
30
31
32#
33# When we also provide SSL we have to listen to the
34# standard HTTP port (see above) and to the HTTPS port
35#
36Listen 443
37
38##
39##  SSL Global Context
40##
41##  All SSL configuration in this context applies both to
42##  the main server and all SSL-enabled virtual hosts.
43##
44
45#   SSL Cipher Suite:
46#   List the ciphers that the client is permitted to negotiate,
47#   and that httpd will negotiate as the client of a proxied server.
48#   See the OpenSSL documentation for a complete list of ciphers, and
49#   ensure these follow appropriate best practices for this deployment.
50#   httpd 2.2.30, 2.4.13 and later force-disable aNULL, eNULL and EXP ciphers,
51#   while OpenSSL disabled these by default in 0.9.8zf/1.0.0r/1.0.1m/1.0.2a.
52#SSLCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES
53#SSLProxyCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES
54SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256
55
56#  By the end of 2016, only TLSv1.2 ciphers should remain in use.
57#  Older ciphers should be disallowed as soon as possible, while the
58#  kRSA ciphers do not offer forward secrecy.  These changes inhibit
59#  older clients (such as IE6 SP2 or IE8 on Windows XP, or other legacy
60#  non-browser tooling) from successfully connecting. 
61#
62#  To restrict mod_ssl to use only TLSv1.2 ciphers, and disable
63#  those protocols which do not support forward secrecy, replace
64#  the SSLCipherSuite and SSLProxyCipherSuite directives above with
65#  the following two directives, as soon as practical.
66# SSLCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA
67# SSLProxyCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA
68
69#   User agents such as web browsers are not configured for the user's
70#   own preference of either security or performance, therefore this
71#   must be the prerogative of the web server administrator who manages
72#   cpu load versus confidentiality, so enforce the server's cipher order.
73SSLHonorCipherOrder on
74
75#   SSL Protocol support:
76#   List the protocol versions which clients are allowed to connect with.
77#   Disable SSLv3 by default (cf. RFC 7525 3.1.1).  TLSv1 (1.0) should be
78#   disabled as quickly as practical.  By the end of 2016, only the TLSv1.2
79#   protocol or later should remain in use.
80#SSLProtocol all -SSLv3
81#SSLProxyProtocol all -SSLv3
82SSLProtocol +TLSv1.2 +TLSv1.3
83
84#   Pass Phrase Dialog:
85#   Configure the pass phrase gathering process.
86#   The filtering dialog program (`builtin' is an internal
87#   terminal dialog) has to provide the pass phrase on stdout.
88SSLPassPhraseDialog  builtin
89
90#   Inter-Process Session Cache:
91#   Configure the SSL Session Cache: First the mechanism
92#   to use and second the expiring timeout (in seconds).
93#SSLSessionCache         "dbm:${SRVROOT}/logs/ssl_scache"
94SSLSessionCache        "shmcb:${SRVROOT}/logs/ssl_scache(512000)"
95SSLSessionCacheTimeout  300
96
97#   OCSP Stapling (requires OpenSSL 0.9.8h or later)
98#
99#   This feature is disabled by default and requires at least
100#   the two directives SSLUseStapling and SSLStaplingCache.
101#   Refer to the documentation on OCSP Stapling in the SSL/TLS
102#   How-To for more information.
103#
104#   Enable stapling for all SSL-enabled servers:
105#SSLUseStapling On
106
107#   Define a relatively small cache for OCSP Stapling using
108#   the same mechanism that is used for the SSL session cache
109#   above.  If stapling is used with more than a few certificates,
110#   the size may need to be increased.  (AH01929 will be logged.)
111#SSLStaplingCache "shmcb:${SRVROOT}/logs/ssl_stapling(32768)"
112
113#   Seconds before valid OCSP responses are expired from the cache
114#SSLStaplingStandardCacheTimeout 3600
115
116#   Seconds before invalid OCSP responses are expired from the cache
117#SSLStaplingErrorCacheTimeout 600
118
119##
120## SSL Virtual Host Context
121##
122
123#<VirtualHost _default_:443>
124
125#   General setup for the virtual host
126#DocumentRoot "${SRVROOT}/htdocs"
127#ServerName www.example.com:443
128#ServerAdmin admin@example.com
129#ErrorLog "${SRVROOT}/logs/error.log"
130#TransferLog "${SRVROOT}/logs/access.log"
131
132#   SSL Engine Switch:
133#   Enable/Disable SSL for this virtual host.
134#SSLEngine on
135
136#   Server Certificate:
137#   Point SSLCertificateFile at a PEM encoded certificate.  If
138#   the certificate is encrypted, then you will be prompted for a
139#   pass phrase.  Note that a kill -HUP will prompt again.  Keep
140#   in mind that if you have both an RSA and a DSA certificate you
141#   can configure both in parallel (to also allow the use of DSA
142#   ciphers, etc.)
143#   Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt)
144#   require an ECC certificate which can also be configured in
145#   parallel.
146#SSLCertificateFile "${SRVROOT}/conf/server.crt"
147#SSLCertificateFile "${SRVROOT}/conf/server-dsa.crt"
148#SSLCertificateFile "${SRVROOT}/conf/server-ecc.crt"
149
150#   Server Private Key:
151#   If the key is not combined with the certificate, use this
152#   directive to point at the key file.  Keep in mind that if
153#   you've both a RSA and a DSA private key you can configure
154#   both in parallel (to also allow the use of DSA ciphers, etc.)
155#   ECC keys, when in use, can also be configured in parallel
156#SSLCertificateKeyFile "${SRVROOT}/conf/server.key"
157#SSLCertificateKeyFile "${SRVROOT}/conf/server-dsa.key"
158#SSLCertificateKeyFile "${SRVROOT}/conf/server-ecc.key"
159
160#   Server Certificate Chain:
161#   Point SSLCertificateChainFile at a file containing the
162#   concatenation of PEM encoded CA certificates which form the
163#   certificate chain for the server certificate. Alternatively
164#   the referenced file can be the same as SSLCertificateFile
165#   when the CA certificates are directly appended to the server
166#   certificate for convenience.
167#SSLCertificateChainFile "${SRVROOT}/conf/server-ca.crt"
168
169#   Certificate Authority (CA):
170#   Set the CA certificate verification path where to find CA
171#   certificates for client authentication or alternatively one
172#   huge file containing all of them (file must be PEM encoded)
173#   Note: Inside SSLCACertificatePath you need hash symlinks
174#         to point to the certificate files. Use the provided
175#         Makefile to update the hash symlinks after changes.
176#SSLCACertificatePath "${SRVROOT}/conf/ssl.crt"
177#SSLCACertificateFile "${SRVROOT}/conf/ssl.crt/ca-bundle.crt"
178
179#   Certificate Revocation Lists (CRL):
180#   Set the CA revocation path where to find CA CRLs for client
181#   authentication or alternatively one huge file containing all
182#   of them (file must be PEM encoded).
183#   The CRL checking mode needs to be configured explicitly
184#   through SSLCARevocationCheck (defaults to "none" otherwise).
185#   Note: Inside SSLCARevocationPath you need hash symlinks
186#         to point to the certificate files. Use the provided
187#         Makefile to update the hash symlinks after changes.
188#SSLCARevocationPath "${SRVROOT}/conf/ssl.crl"
189#SSLCARevocationFile "${SRVROOT}/conf/ssl.crl/ca-bundle.crl"
190#SSLCARevocationCheck chain
191
192#   Client Authentication (Type):
193#   Client certificate verification type and depth.  Types are
194#   none, optional, require and optional_no_ca.  Depth is a
195#   number which specifies how deeply to verify the certificate
196#   issuer chain before deciding the certificate is not valid.
197#SSLVerifyClient require
198#SSLVerifyDepth  10
199
200#   TLS-SRP mutual authentication:
201#   Enable TLS-SRP and set the path to the OpenSSL SRP verifier
202#   file (containing login information for SRP user accounts).
203#   Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for
204#   detailed instructions on creating this file. Example:
205#   "openssl srp -srpvfile ${SRVROOT}/conf/passwd.srpv -add username"
206#SSLSRPVerifierFile "${SRVROOT}/conf/passwd.srpv"
207
208#   Access Control:
209#   With SSLRequire you can do per-directory access control based
210#   on arbitrary complex boolean expressions containing server
211#   variable checks and other lookup directives.  The syntax is a
212#   mixture between C and Perl.  See the mod_ssl documentation
213#   for more details.
214#<Location />
215#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
216#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
217#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
218#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
219#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
220#           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
221#</Location>
222
223#   SSL Engine Options:
224#   Set various options for the SSL engine.
225#   o FakeBasicAuth:
226#     Translate the client X.509 into a Basic Authorisation.  This means that
227#     the standard Auth/DBMAuth methods can be used for access control.  The
228#     user name is the `one line' version of the client's X.509 certificate.
229#     Note that no password is obtained from the user. Every entry in the user
230#     file needs this password: `xxj31ZMTZzkVA'.
231#   o ExportCertData:
232#     This exports two additional environment variables: SSL_CLIENT_CERT and
233#     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
234#     server (always existing) and the client (only existing when client
235#     authentication is used). This can be used to import the certificates
236#     into CGI scripts.
237#   o StdEnvVars:
238#     This exports the standard SSL/TLS related `SSL_*' environment variables.
239#     Per default this exportation is switched off for performance reasons,
240#     because the extraction step is an expensive operation and is usually
241#     useless for serving static content. So one usually enables the
242#     exportation for CGI and SSI requests only.
243#   o StrictRequire:
244#     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
245#     under a "Satisfy any" situation, i.e. when it applies access is denied
246#     and no other module can change it.
247#   o OptRenegotiate:
248#     This enables optimized SSL connection renegotiation handling when SSL
249#     directives are used in per-directory context.
250#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
251<FilesMatch "\.(cgi|shtml|phtml|php)$">
252    SSLOptions +StdEnvVars
253</FilesMatch>
254<Directory "${SRVROOT}/cgi-bin">
255    SSLOptions +StdEnvVars
256</Directory>
257
258#   SSL Protocol Adjustments:
259#   The safe and default but still SSL/TLS standard compliant shutdown
260#   approach is that mod_ssl sends the close notify alert but doesn't wait for
261#   the close notify alert from client. When you need a different shutdown
262#   approach you can use one of the following variables:
263#   o ssl-unclean-shutdown:
264#     This forces an unclean shutdown when the connection is closed, i.e. no
265#     SSL close notify alert is sent or allowed to be received.  This violates
266#     the SSL/TLS standard but is needed for some brain-dead browsers. Use
267#     this when you receive I/O errors because of the standard approach where
268#     mod_ssl sends the close notify alert.
269#   o ssl-accurate-shutdown:
270#     This forces an accurate shutdown when the connection is closed, i.e. a
271#     SSL close notify alert is send and mod_ssl waits for the close notify
272#     alert of the client. This is 100% SSL/TLS standard compliant, but in
273#     practice often causes hanging connections with brain-dead browsers. Use
274#     this only for browsers where you know that their SSL implementation
275#     works correctly.
276#   Notice: Most problems of broken clients are also related to the HTTP
277#   keep-alive facility, so you usually additionally want to disable
278#   keep-alive for those clients, too. Use variable "nokeepalive" for this.
279#   Similarly, one has to force some clients to use HTTP/1.0 to workaround
280#   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
281#   "force-response-1.0" for this.
282#BrowserMatch "MSIE [2-5]" \
283#         nokeepalive ssl-unclean-shutdown \
284#         downgrade-1.0 force-response-1.0
285
286#   Per-Server Logging:
287#   The home of a custom SSL log file. Use this when you want a
288#   compact non-error SSL logfile on a virtual host basis.
289#CustomLog "${SRVROOT}/logs/ssl_request.log" \
290          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
291
292#</VirtualHost>                                 
Note: See TracBrowser for help on using the repository browser.