1 %%\subsection{Webservers}
3 %%----------------------------------------------------------------------
6 \subsubsection{Tested with Version} \todo{FIXME: add}
8 \subsubsection{Settings}
10 %-All +TLSv1.1 +TLSv1.2
11 \begin{lstlisting}[breaklines]
12 SSLProtocol All -SSLv2 -SSLv3
13 SSLHonorCipherOrder On
15 # Add six earth month HSTS header for all users...
16 Header add Strict-Transport-Security "max-age=15768000"
17 # If you want to protect all subdomains, use the following header
18 # ALL subdomains HAVE TO support https if you use this!
19 # Strict-Transport-Security: max-age=15768000 ; includeSubDomains
21 SSLCipherSuite '@@@CIPHERSTRINGB@@@'
25 Note again, that any cipher suite starting with ECDHE can be omitted, if in doubt.
29 \subsubsection{Additional settings}
31 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:
33 \begin{lstlisting}[breaklines]
37 RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R=permanent]
42 \subsubsection{Justification for special settings (if needed)}
44 \subsubsection{References}
46 \subsubsection{How to test}
48 See section \ref{section:Tools}
53 %%----------------------------------------------------------------------
59 \subsubsection{Tested with Version}
63 \subsubsection{Settings}
66 %% Complete ssl.cipher-list with same algo than Apache
67 \todo{FIXME: this string seems to be wrongly formatted??}
69 \begin{lstlisting}[breaklines]
70 $SERVER["socket"] == "0.0.0.0:443" {
72 ssl.use-sslv2 = "disable"
73 ssl.use-sslv3 = "disable"
74 #ssl.use-compression obsolete >= 1.4.3.1
75 ssl.pemfile = "/etc/lighttpd/server.pem"
76 ssl.cipher-list = '@@@CIPHERSTRINGB@@@'
77 ssl.honor-cipher-order = "enable"
78 setenv.add-response-header = ( "Strict-Transport-Security" => "max-age=31536000")
83 \subsubsection{Additional settings}
85 As for any other webserver, you might want to automatically redirect http traffic toward httpS://
87 \begin{lstlisting}[breaklines]
88 $HTTP["scheme"] == "http" {
89 # capture vhost name with regex conditiona -> %0 in redirect pattern
90 # must be the most inner block to the redirect rule
91 $HTTP["host"] =~ ".*" {
92 url.redirect = (".*" => "https://%0$0")
98 \subsubsection{References} \todo{add references to lighttpd SSL settins documentation}.
100 lighttpd httpS:// redirection: \url{http://redmine.lighttpd.net/projects/1/wiki/HowToRedirectHttpToHttps}
103 \subsubsection{How to test}
104 See section \ref{section:Tools}
106 % describe here or point the admin to tools (can be a simple footnote or \ref{} to the tools section) which help the admin to test his settings.
110 %%----------------------------------------------------------------------
114 \subsubsection{Tested with Version}
116 \item 1.4.4 with OpenSSL 1.0.1e on OS X Server 10.8.5
117 \item 1.2.1-2.2+wheezy2 with OpenSSL 1.0.1e on Debian Wheezy
118 \item 1.4.4 with OpenSSL 1.0.1e on Debian Wheezy
119 \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)
123 \subsubsection{Settings}
125 \begin{lstlisting}[breaklines]
126 ssl_prefer_server_ciphers on;
127 ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # not possible to do exclusive
128 ssl_ciphers '@@@CIPHERSTRINGB@@@';
129 add_header Strict-Transport-Security max-age=2592000;
132 If you absolutely want to specify your own DH parameters, you can specify them via
134 \begin{lstlisting}[breaklines]
138 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).
141 \subsubsection{Additional settings}
143 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:
145 \begin{lstlisting}[breaklines]
146 ssl_ecdh_curve secp384r1;
149 You might want to redirect everything to httpS:// if possible. In Nginx you can do this with the following setting:
151 \begin{lstlisting}[breaklines]
152 rewrite ^(.*) https://$host$1 permanent;
156 \subsubsection{References} \todo{add references}
158 \subsubsection{How to test}
159 See section \ref{section:Tools}
167 %%----------------------------------------------------------------------
172 \todo{Daniel: add screenshots and registry keys}
176 \subsubsection{Tested with Version} \todo{Daniel: add tested version}
178 \subsubsection{Settings}
181 When trying to avoid RC4 and CBC (BEAST-Attack) and requiring perfect
182 forward secrecy, Microsoft Internet Information Server (IIS) supports
183 ECDSA, but does not support RSA for key exchange (consider ECC suite
184 B doubts\footnote{\url{http://safecurves.cr.yp.to/rigid.html}}).
186 Since \verb|ECDHE_RSA_*| is not supported, a SSL certificate based on
187 elliptic curves needs to be used.
189 The configuration of cipher suites MS IIS will use, can be configured in one
190 of the following ways:
192 \item Group Policy \footnote{\url{http://msdn.microsoft.com/en-us/library/windows/desktop/bb870930(v=vs.85).aspx}}
194 \item IIS Crypto~\footnote{\url{https://www.nartac.com/Products/IISCrypto/}}
198 Table~\ref{tab:MS_IIS_Client_Support} shows the process of turning on
199 one algorithm after another and the effect on the supported clients
200 tested using https://www.ssllabs.com.
202 \verb|SSL 3.0|, \verb|SSL 2.0| and \verb|MD5| are turned off.
203 \verb|TLS 1.0| and \verb|TLS 2.0| are turned on.
210 Cipher Suite & Client \\
212 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| & only IE 10,11, OpenSSL 1.0.1e \\
213 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| & Chrome 30, Opera 17, Safari 6+ \\
214 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| & FF 10-24, IE 8+, Safari 5, Java 7\\
217 \caption{Client support}
218 \label{tab:MS_IIS_Client_Support}
221 Table~\ref{tab:MS_IIS_Client_Support} shows the algoriths from
222 strongest to weakest and why they need to be added in this order. For
223 example insisting on SHA-2 algorithms (only first two lines) would
224 eliminate all versions of Firefox, so the last line is needed to
225 support this browser, but should be placed at the bottom, so capable
226 browsers will choose the stronger SHA-2 algorithms.
228 \verb|TLS_RSA_WITH_RC4_128_SHA| or equivalent should also be added if
229 MS Terminal Server Connection is used (make sure to use this only in a
230 trusted environment). This suite will not be used for SSL, since we do
234 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| ... only supported by: IE 10,11, OpenSSL 1.0.1e
235 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| ... Chrome 30, Opera 17, Safari 6+
236 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| ... Firefox 10-24, IE 8+, Safari 5, Java 7
239 Clients not supported:
246 \subsubsection{Additional settings}
248 %Here you can add additional settings
250 \subsubsection{Justification for special settings (if needed)}
252 % 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
254 \subsubsection{References}
256 \todo{add references}
258 % add any further references or best practice documents here
260 \subsubsection{How to test}
261 See section \ref{section:Tools}