1 %%\subsection{Webservers}
3 %%----------------------------------------------------------------------
6 \subsubsection{Tested with Versions}
8 \item Apache 2.4.6 linked against OpenSSL 1.0.1e, Debian jessie
12 \subsubsection{Settings}
14 Enabled modules \emph{SSL} and \emph{Headers} are required.
16 %-All +TLSv1.1 +TLSv1.2
17 \begin{lstlisting}[breaklines]
18 SSLCertificateFile server.crt
19 SSLCertificateKeyFile server.key
20 SSLProtocol All -SSLv2 -SSLv3
21 SSLHonorCipherOrder On
23 # Add six earth month HSTS header for all users...
24 Header add Strict-Transport-Security "max-age=15768000"
25 # If you want to protect all subdomains, use the following header
26 # ALL subdomains HAVE TO support https if you use this!
27 # Strict-Transport-Security: max-age=15768000 ; includeSubDomains
29 SSLCipherSuite '@@@CIPHERSTRINGB@@@'
33 Note that any cipher suite starting with ECDHE can be omitted, if in doubt.
35 \subsubsection{Additional settings}
37 You might want to redirect everything to httpS:// if possible. In Apache you can do this with the following setting inside of a VirtualHost environment:
39 \begin{lstlisting}[breaklines]
43 RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R=permanent]
48 %\subsubsection{Justification for special settings (if needed)}
50 \subsubsection{References}
51 \url{https://httpd.apache.org/docs/2.4/ssl/}
54 \subsubsection{How to test}
56 See appendix \ref{cha:tools}
61 %%----------------------------------------------------------------------
67 \subsubsection{Tested with Version}
69 \item lighttpd/1.4.31-4 with OpenSSL 1.0.1e on Debian Wheezy
70 \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)
71 \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)
75 \subsubsection{Settings}
78 %% Complete ssl.cipher-list with same algo than Apache
79 \todo{FIXME: this string seems to be wrongly formatted??}
81 \begin{lstlisting}[breaklines]
82 $SERVER["socket"] == "0.0.0.0:443" {
84 ssl.use-sslv2 = "disable"
85 ssl.use-sslv3 = "disable"
86 #ssl.use-compression obsolete >= 1.4.3.1
87 ssl.pemfile = "/etc/lighttpd/server.pem"
88 ssl.cipher-list = "@@@CIPHERSTRINGB@@@"
89 ssl.honor-cipher-order = "enable"
90 setenv.add-response-header = ( "Strict-Transport-Security" => "max-age=31536000")
95 \subsubsection{Additional settings}
97 As for any other webserver, you might want to automatically redirect http
98 traffic toward httpS:// It is also recommended to set the environment variable
99 \emph{HTTPS}, so the applications run by the webserver can easily detect, that
104 \begin{lstlisting}[breaklines]
105 $HTTP["scheme"] == "http" {
106 # capture vhost name with regex conditiona -> %0 in redirect pattern
107 # must be the most inner block to the redirect rule
108 $HTTP["host"] =~ ".*" {
109 url.redirect = (".*" => "https://%0$0")
112 # Set the environment variable properly
113 setenv.add-environment = (
120 \subsubsection{Additional information}
121 The config option \emph{honor-cipher-order} is available since 1.4.30, the
122 supported ciphers depend on the used OpenSSL-version (at runtime). ECDH has to
123 be available in OpenSSL at compile-time, which should be default. SSL
124 compression should by deactivated by default at compile-time (if not, it's
127 Support for other SSL-libraries like GnuTLS will be available in the upcoming
128 2.x branch, which is currently under development.
131 \subsubsection{References}
134 \item HTTPS redirection: \url{http://redmine.lighttpd.net/projects/1/wiki/HowToRedirectHttpToHttps}
135 \item Lighttpd Docs SSL: \url{http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs\_SSL}
136 \item Release 1.4.30 (How to mitigate BEAST attack) \url{http://redmine.lighttpd.net/projects/lighttpd/wiki/Release-1\_4\_30}
137 \item SSL Compression disabled by default: \url{http://redmine.lighttpd.net/issues/2445}
143 \subsubsection{How to test}
144 See appendix \ref{cha:tools}
148 %%----------------------------------------------------------------------
152 \subsubsection{Tested with Version}
154 \item 1.4.4 with OpenSSL 1.0.1e on OS X Server 10.8.5
155 \item 1.2.1-2.2+wheezy2 with OpenSSL 1.0.1e on Debian Wheezy
156 \item 1.4.4 with OpenSSL 1.0.1e on Debian Wheezy
157 \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)
161 \subsubsection{Settings}
163 \begin{lstlisting}[breaklines]
164 ssl_prefer_server_ciphers on;
165 ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # not possible to do exclusive
166 ssl_ciphers '@@@CIPHERSTRINGB@@@';
167 add_header Strict-Transport-Security max-age=2592000;
170 If you absolutely want to specify your own DH parameters, you can specify them via
172 \begin{lstlisting}[breaklines]
176 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).
178 \subsubsection{Additional settings}
180 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:
182 \begin{lstlisting}[breaklines]
183 ssl_ecdh_curve secp384r1;
186 You might want to redirect everything to httpS:// if possible. In Nginx you can do this with the following setting:
188 \begin{lstlisting}[breaklines]
189 rewrite ^(.*) https://$host$1 permanent;
193 \subsubsection{References}
195 \item \url{http://nginx.org/en/docs/http/ngx_http_ssl_module.html}
196 \item \url{http://wiki.nginx.org/HttpSslModule}
199 \subsubsection{How to test}
200 See appendix \ref{cha:tools}
206 %%----------------------------------------------------------------------
211 \todo{Daniel: add screenshots and registry keys}
215 \subsubsection{Tested with Version} \todo{Daniel: add tested version}
217 \subsubsection{Settings}
220 When trying to avoid RC4 and CBC (BEAST-Attack) and requiring perfect
221 forward secrecy, Microsoft Internet Information Server (IIS) supports
222 ECDSA, but does not support RSA for key exchange (consider ECC suite
223 B doubts\footnote{\url{http://safecurves.cr.yp.to/rigid.html}}).
225 Since \verb|ECDHE_RSA_*| is not supported, a SSL certificate based on
226 elliptic curves needs to be used.
228 The configuration of cipher suites MS IIS will use, can be configured in one
229 of the following ways:
231 \item Group Policy \footnote{\url{http://msdn.microsoft.com/en-us/library/windows/desktop/bb870930(v=vs.85).aspx}}
233 \item IIS Crypto~\footnote{\url{https://www.nartac.com/Products/IISCrypto/}}
237 Table~\ref{tab:MS_IIS_Client_Support} shows the process of turning on
238 one algorithm after another and the effect on the supported clients
239 tested using https://www.ssllabs.com.
241 \verb|SSL 3.0|, \verb|SSL 2.0| and \verb|MD5| are turned off.
242 \verb|TLS 1.0| and \verb|TLS 2.0| are turned on.
249 Cipher Suite & Client \\
251 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| & only IE 10,11, OpenSSL 1.0.1e \\
252 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| & Chrome 30, Opera 17, Safari 6+ \\
253 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| & FF 10-24, IE 8+, Safari 5, Java 7\\
256 \caption{Client support}
257 \label{tab:MS_IIS_Client_Support}
260 Table~\ref{tab:MS_IIS_Client_Support} shows the algorithms from
261 strongest to weakest and why they need to be added in this order. For
262 example insisting on SHA-2 algorithms (only first two lines) would
263 eliminate all versions of Firefox, so the last line is needed to
264 support this browser, but should be placed at the bottom, so capable
265 browsers will choose the stronger SHA-2 algorithms.
267 \verb|TLS_RSA_WITH_RC4_128_SHA| or equivalent should also be added if
268 MS Terminal Server Connection is used (make sure to use this only in a
269 trusted environment). This suite will not be used for SSL, since we do
273 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| ... only supported by: IE 10,11, OpenSSL 1.0.1e
274 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| ... Chrome 30, Opera 17, Safari 6+
275 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| ... Firefox 10-24, IE 8+, Safari 5, Java 7
278 Clients not supported:
285 \subsubsection{Additional settings}
287 %Here you can add additional settings
289 \subsubsection{Justification for special settings (if needed)}
291 % 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
293 \subsubsection{References}
295 \todo{add references}
297 % add any further references or best practice documents here
299 \subsubsection{How to test}
300 See appendix \ref{cha:tools}
307 %%% TeX-master: "../applied-crypto-hardening"