1 %%\subsection{Webservers}
6 \item[Tested with Version:]
8 \item[Settings:] \mbox{}
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
22 SSLCipherSuite 'EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EDH+CAMELLIA256:EECDH:EDH+aRSA:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:!SEED:!AES128:!CAMELLIA128:!ECDSA:AES256-SHA'
24 SSLCipherSuite '@@@CIPHERSTRINGB@@@'
28 Note again, that any cipher suite starting with ECDHE can be omitted, if in doubt.
29 %% XXX NOTE TO SELF: remove from future automatically generated lists!
31 \item[Additional settings:]
33 You should redirect everything to httpS:// if possible. In Apache you can do this with the following setting inside of a VirtualHost environment:
35 \begin{lstlisting}[breaklines]
39 RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R=permanent]
44 \item[Justification for special settings (if needed):]
50 See ssllabs in section \ref{section:Tools}
53 %XXXX ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AES:RSA+3DES:!ADH:!AECDH:!MD5:!DSS
56 \subsubsection{lighttpd}
61 \item[Tested with Version:]
65 \item[Settings:] \mbox{}
68 %% Complete ssl.cipher-list with same algo than Apache
69 \todo{FIXME: this string seems to be wrongly formatted??}
71 \begin{lstlisting}[breaklines]
72 $SERVER["socket"] == "0.0.0.0:443" {
74 ssl.use-sslv2 = "disable"
75 ssl.use-sslv3 = "disable"
76 #ssl.use-compression obsolete >= 1.4.3.1
77 ssl.pemfile = "/etc/lighttpd/server.pem"
78 ssl.cipher-list = 'EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EDH+CAMELLIA256:EECDH:EDH+aRSA:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:!SEED:!AES128:!CAMELLIA128:!ECDSA:AES256-SHA'
79 ssl.honor-cipher-order = "enable"
80 setenv.add-response-header = ( "Strict-Transport-Security" => "max-age=31536000")
85 \item[Additional settings:]
87 As for any other webserver, you should automatically redirect http traffic toward httpS://
89 \begin{lstlisting}[breaklines]
90 $HTTP["scheme"] == "http" {
91 # capture vhost name with regex conditiona -> %0 in redirect pattern
92 # must be the most inner block to the redirect rule
93 $HTTP["host"] =~ ".*" {
94 url.redirect = (".*" => "https://%0$0")
101 \todo{add references}.
102 lighttpd httpS:// redirection: \url{http://redmine.lighttpd.net/projects/1/wiki/HowToRedirectHttpToHttps}
104 % add any further references or best practice documents here
106 \item[How to test:] See ssllabs in section \ref{section:Tools}
108 % 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.
112 \subsubsection{nginx}
115 \item[Tested with Version:] 1.4.4 with OpenSSL 1.0.1e on OS X Server 10.8.5
117 1.2.1-2.2+wheezy2 with OpenSSL 1.0.1e on Debian Wheezy
118 1.4.4 with OpenSSL 1.0.1e on Debian Wheezy
119 1.4.4 with OpenSSL 1.0.1e on Debian Wheezy
120 1.4.4 with OpenSSL 1.0.1e on Debian Wheezy
121 1.4.4 with OpenSSL 1.0.1e on Debian Wheezy
125 \item[Settings:] \mbox{}
127 \begin{lstlisting}[breaklines]
128 ssl_prefer_server_ciphers on;
129 ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
130 ssl_ciphers 'EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EDH+CAMELLIA256:EECDH:EDH+aRSA:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:!SEED:!AES128:!CAMELLIA128:!ECDSA:AES256-SHA';
131 add_header Strict-Transport-Security max-age=2592000;
134 %% XXX FIXME: do we need to specify dhparams? Parameter: ssl_dhparam = file. See: http://wiki.nginx.org/HttpSslModule#ssl_protocols
137 If you absolutely want to specify your own DH parameters, you can specify them via
139 \begin{lstlisting}[breaklines]
143 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).
146 \item[Additional settings:]
148 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:
150 \begin{lstlisting}[breaklines]
151 ssl_ecdh_curve secp384r1;
154 You should redirect everything to httpS:// if possible. In Nginx you can do this with the following setting:
156 \begin{lstlisting}[breaklines]
157 rewrite ^(.*) https://$host$1 permanent;
161 \item[References:] \todo{add references}
163 \item[How to test:] See ssllabs in section \ref{section:Tools}
171 \subsubsection{MS IIS}
175 \todo{Daniel: add screenshots and registry keys}
179 \item[Tested with Version:] \todo{Daniel: add tested version}
181 \item[Settings:] \mbox{}
184 When trying to avoid RC4 and CBC (BEAST-Attack) and requiring perfect
185 forward secrecy, Microsoft Internet Information Server (IIS) supports
186 ECDSA, but does not support RSA for key exchange (consider ECC suite
187 B doubts\footnote{\url{http://safecurves.cr.yp.to/rigid.html}}).
189 Since \verb|ECDHE_RSA_*| is not supported, a SSL certificate based on
190 elliptic curves needs to be used.
192 The configuration of cipher suites MS IIS will use, can be configured in one
193 of the following ways:
195 \item Group Policy \footnote{\url{http://msdn.microsoft.com/en-us/library/windows/desktop/bb870930(v=vs.85).aspx}}
197 \item IIS Crypto~\footnote{\url{https://www.nartac.com/Products/IISCrypto/}}
201 Table~\ref{tab:MS_IIS_Client_Support} shows the process of turning on
202 one algorithm after another and the effect on the supported clients
203 tested using https://www.ssllabs.com.
205 \verb|SSL 3.0|, \verb|SSL 2.0| and \verb|MD5| are turned off.
206 \verb|TLS 1.0| and \verb|TLS 2.0| are turned on.
213 Cipher Suite & Client \\
215 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| & only IE 10,11, OpenSSL 1.0.1e \\
216 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| & Chrome 30, Opera 17, Safari 6+ \\
217 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| & FF 10-24, IE 8+, Safari 5, Java 7\\
220 \caption{Client support}
221 \label{tab:MS_IIS_Client_Support}
224 Table~\ref{tab:MS_IIS_Client_Support} shows the algoriths from
225 strongest to weakest and why they need to be added in this order. For
226 example insisting on SHA-2 algorithms (only first two lines) would
227 eliminate all versions of Firefox, so the last line is needed to
228 support this browser, but should be placed at the bottom, so capable
229 browsers will choose the stronger SHA-2 algorithms.
231 \verb|TLS_RSA_WITH_RC4_128_SHA| or equivalent should also be added if
232 MS Terminal Server Connection is used (make sure to use this only in a
233 trusted environment). This suite will not be used for SSL, since we do
237 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| ... only supported by: IE 10,11, OpenSSL 1.0.1e
238 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| ... Chrome 30, Opera 17, Safari 6+
239 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| ... Firefox 10-24, IE 8+, Safari 5, Java 7
242 Clients not supported:
249 \item[Additional settings:]
251 %Here you can add additional settings
253 \item[Justification for special settings (if needed):]
255 % 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
259 \todo{add references}
261 % add any further references or best practice documents here
263 \item[How to test:] See ssllabs in section \ref{section:Tools}