1 %%\subsection{Webservers}
3 %%----------------------------------------------------------------------
6 \subsubsection{Tested with Versions}
8 \item Apache 2.2.22 linked against OpenSSL 1.0.1e, Debian Wheezy
9 \item Apache 2.4.6 linked against OpenSSL 1.0.1e, Debian Jessie
13 \subsubsection{Settings}
15 Enabled modules \emph{SSL} and \emph{Headers} are required.
17 %-All +TLSv1.1 +TLSv1.2
18 \begin{lstlisting}[breaklines]
19 SSLCertificateFile server.crt
20 SSLCertificateKeyFile server.key
21 SSLProtocol All -SSLv2 -SSLv3
22 SSLHonorCipherOrder On
24 # Add six earth month HSTS header for all users...
25 Header add Strict-Transport-Security "max-age=15768000"
26 # If you want to protect all subdomains, use the following header
27 # ALL subdomains HAVE TO support https if you use this!
28 # Strict-Transport-Security: max-age=15768000 ; includeSubDomains
30 SSLCipherSuite '@@@CIPHERSTRINGB@@@'
34 Note that any cipher suite starting with EECDH can be omitted, if in doubt.
35 (Compared to the theory section, EECDH in Apache and ECDHE in OpenSSL are
36 synonyms~\footnote{https://www.mail-archive.com/openssl-dev@openssl.org/msg33405.html})
38 \subsubsection{Additional settings}
40 You might want to redirect everything to http\textbf{s}:// if possible. In Apache you can do this with the following setting inside of a VirtualHost environment:
42 \begin{lstlisting}[breaklines]
46 RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R=permanent]
51 %\subsubsection{Justification for special settings (if needed)}
53 \subsubsection{References}
54 \url{https://httpd.apache.org/docs/2.4/ssl/}
57 \subsubsection{How to test}
59 See appendix \ref{cha:tools}
64 %%----------------------------------------------------------------------
67 \todo{sebix: add/test ssl.ec-curve and ssl.dh-file; see \url{http://redmine.lighttpd.net/projects/1/wiki/Docsr\_SSL\#Diffie-Hellman-and-Elliptic-Curve-Diffie-Hellman-parameters}}
70 \subsubsection{Tested with Version}
72 \item lighttpd/1.4.31-4 with OpenSSL 1.0.1e on Debian Wheezy
73 \item lighttpd/1.4.33 with OpenSSL 0.9.8o on Debian Squeeze (note that TLSv1.2 does not work in openssl 0.9.8 thus not all ciphers actually work)
74 \item lighttpd/1.4.28-2 with OpenSSL 0.9.8o on Debian Squeeze (note that TLSv1.2 does not work in openssl 0.9.8 thus not all ciphers actually work)
78 \subsubsection{Settings}
81 %% Complete ssl.cipher-list with same algo than Apache
82 \todo{FIXME: this string seems to be wrongly formatted??}
84 \begin{lstlisting}[breaklines]
85 $SERVER["socket"] == "0.0.0.0:443" {
87 ssl.use-sslv2 = "disable"
88 ssl.use-sslv3 = "disable"
89 #ssl.use-compression obsolete >= 1.4.3.1
90 ssl.pemfile = "/etc/lighttpd/server.pem"
91 ssl.cipher-list = "@@@CIPHERSTRINGB@@@"
92 ssl.honor-cipher-order = "enable"
93 setenv.add-response-header = ( "Strict-Transport-Security" => "max-age=31536000")
98 \subsubsection{Additional settings}
100 As for any other webserver, you might want to automatically redirect http
101 traffic toward http\textbf{s}:// It is also recommended to set the environment variable
102 \emph{HTTPS}, so the applications run by the webserver can easily detect, that
107 \begin{lstlisting}[breaklines]
108 $HTTP["scheme"] == "http" {
109 # capture vhost name with regex conditiona -> %0 in redirect pattern
110 # must be the most inner block to the redirect rule
111 $HTTP["host"] =~ ".*" {
112 url.redirect = (".*" => "https://%0$0")
114 # Set the environment variable properly
115 setenv.add-environment = (
122 \subsubsection{Additional information}
123 The config option \emph{honor-cipher-order} is available since 1.4.30, the
124 supported ciphers depend on the used OpenSSL-version (at runtime). ECDH has to
125 be available in OpenSSL at compile-time, which should be default. SSL
126 compression should by deactivated by default at compile-time (if not, it's
129 Support for other SSL-libraries like GnuTLS will be available in the upcoming
130 2.x branch, which is currently under development.
133 \subsubsection{References}
136 \item HTTPS redirection: \url{http://redmine.lighttpd.net/projects/1/wiki/HowToRedirectHttpToHttps}
137 \item Lighttpd Docs SSL: \url{http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs\_SSL}
138 \item Release 1.4.30 (How to mitigate BEAST attack) \url{http://redmine.lighttpd.net/projects/lighttpd/wiki/Release-1\_4\_30}
139 \item SSL Compression disabled by default: \url{http://redmine.lighttpd.net/issues/2445}
145 \subsubsection{How to test}
146 See appendix \ref{cha:tools}
150 %%----------------------------------------------------------------------
154 \subsubsection{Tested with Version}
156 \item 1.4.4 with OpenSSL 1.0.1e on OS X Server 10.8.5
157 \item 1.2.1-2.2+wheezy2 with OpenSSL 1.0.1e on Debian Wheezy
158 \item 1.4.4 with OpenSSL 1.0.1e on Debian Wheezy
159 \item 1.2.1-2.2~bpo60+2 with OpenSSL 0.9.8o on Debian Squeeze (note that TLSv1.2 does not work in openssl 0.9.8 thus not all ciphers actually work)
163 \subsubsection{Settings}
165 \begin{lstlisting}[breaklines]
166 ssl_prefer_server_ciphers on;
167 ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # not possible to do exclusive
168 ssl_ciphers '@@@CIPHERSTRINGB@@@';
169 add_header Strict-Transport-Security max-age=2592000;
172 If you absolutely want to specify your own DH parameters, you can specify them via
174 \begin{lstlisting}[breaklines]
178 However, we advise you to read section \ref{section:DH} and stay with the standard IKE/IETF parameters (as long as they are $ > 1024 $ bits).
180 \subsubsection{Additional settings}
182 If you decide to trust NIST's ECC curve recommendation, you can add the following line to nginx's configuration file to select special curves:
184 \begin{lstlisting}[breaklines]
185 ssl_ecdh_curve secp384r1;
188 You might want to redirect everything to http\textbf{s}:// if possible. In Nginx you can do this with the following setting:
190 \begin{lstlisting}[breaklines]
191 return 301 https://$host$request_uri;
195 \subsubsection{References}
197 \item \url{http://nginx.org/en/docs/http/ngx_http_ssl_module.html}
198 \item \url{http://wiki.nginx.org/HttpSslModule}
201 \subsubsection{How to test}
202 See appendix \ref{cha:tools}
208 %%----------------------------------------------------------------------
213 \todo{Daniel: add screenshots and registry keys}
217 \subsubsection{Tested with Version} \todo{Daniel: add tested version}
219 \subsubsection{Settings}
222 When trying to avoid RC4 and CBC (BEAST-Attack) and requiring perfect
223 forward secrecy, Microsoft Internet Information Server (IIS) supports
224 ECDSA, but does not support RSA for key exchange (consider ECC suite
225 B doubts\footnote{\url{http://safecurves.cr.yp.to/rigid.html}}).
227 Since \verb|ECDHE_RSA_*| is not supported, a SSL certificate based on
228 elliptic curves needs to be used.
230 The configuration of cipher suites MS IIS will use, can be configured in one
231 of the following ways:
233 \item Group Policy \footnote{\url{http://msdn.microsoft.com/en-us/library/windows/desktop/bb870930(v=vs.85).aspx}}
235 \item IIS Crypto~\footnote{\url{https://www.nartac.com/Products/IISCrypto/}}
239 Table~\ref{tab:MS_IIS_Client_Support} shows the process of turning on
240 one algorithm after another and the effect on the supported clients
241 tested using https://www.ssllabs.com.
243 \verb|SSL 3.0|, \verb|SSL 2.0| and \verb|MD5| are turned off.
244 \verb|TLS 1.0| and \verb|TLS 2.0| are turned on.
251 Cipher Suite & Client \\
253 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| & only IE 10,11, OpenSSL 1.0.1e \\
254 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| & Chrome 30, Opera 17, Safari 6+ \\
255 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| & FF 10-24, IE 8+, Safari 5, Java 7\\
258 \caption{Client support}
259 \label{tab:MS_IIS_Client_Support}
262 Table~\ref{tab:MS_IIS_Client_Support} shows the algorithms from
263 strongest to weakest and why they need to be added in this order. For
264 example insisting on SHA-2 algorithms (only first two lines) would
265 eliminate all versions of Firefox, so the last line is needed to
266 support this browser, but should be placed at the bottom, so capable
267 browsers will choose the stronger SHA-2 algorithms.
269 \verb|TLS_RSA_WITH_RC4_128_SHA| or equivalent should also be added if
270 MS Terminal Server Connection is used (make sure to use this only in a
271 trusted environment). This suite will not be used for SSL, since we do
275 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| ... only supported by: IE 10,11, OpenSSL 1.0.1e
276 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| ... Chrome 30, Opera 17, Safari 6+
277 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| ... Firefox 10-24, IE 8+, Safari 5, Java 7
280 Clients not supported:
287 \subsubsection{Additional settings}
289 %Here you can add additional settings
291 \subsubsection{Justification for special settings (if needed)}
293 % in case you have the need for further justifications why you chose this and that setting or if the settings do not fit into the standard Variant A or Variant B schema, please document this here
295 \subsubsection{References}
297 \todo{add references}
299 % add any further references or best practice documents here
301 \subsubsection{How to test}
302 See appendix \ref{cha:tools}
309 %%% TeX-master: "../applied-crypto-hardening"