1 \section{Recommendations on practical settings}
4 \subsection{Webservers}
9 \item[Tested with Version:]
11 \item[Settings:] \mbox{}
13 %-All +TLSv1.1 +TLSv1.2
14 \begin{lstlisting}[breaklines]
15 SSLProtocol All -SSLv2 -SSLv3
16 SSLHonorCipherOrder On
18 # Add six earth month HSTS header for all users...
19 Header add Strict-Transport-Security "max-age=15768000"
20 # If you want to protect all subdomains, use the following header
21 # ALL subdomains HAVE TO support https if you use this!
22 # Strict-Transport-Security: max-age=15768000 ; includeSubDomains
24 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'
27 Note again, that any cipher suite starting with ECDHE can be omitted in case of doubt.
28 %% XXX NOTE TO SELF: remove from future automatically generated lists!
30 \item[Additional settings:]
32 You should redirect everything to httpS:// if possible. In Apache you can do this with the following setting inside of a VirtualHost environment:
34 \begin{lstlisting}[breaklines]
38 RewriteRule ^.*$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R=permanent]
43 \item[Justification for special settings (if needed):]
48 %XXXX ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AES:RSA+3DES:!ADH:!AECDH:!MD5:!DSS
51 \subsubsection{lighttpd}
55 %% Note: need to be checked / reviewed
57 %% Complete ssl.cipher-list with same algo than Apache
58 \todo{FIXME: this string seems to be wrongly formatted}
60 \begin{lstlisting}[breaklines]
61 $SERVER["socket"] == "0.0.0.0:443" {
63 ssl.use-sslv2 = "disable"
64 ssl.use-sslv3 = "disable"
65 #ssl.use-compression obsolete >= 1.4.3.1
66 ssl.pemfile = "/etc/lighttpd/server.pem"
67 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'
68 ssl.honor-cipher-order = "enable"
69 setenv.add-response-header = ( "Strict-Transport-Security" => "max-age=31536000")
73 As for any other webserver, you should redirect automatically http traffic toward httpS:\footnote{That proposed configuration is directly coming from lighttpd documentation: \url{http://redmine.lighttpd.net/projects/1/wiki/HowToRedirectHttpToHttps}}
75 \begin{lstlisting}[breaklines]
76 $HTTP["scheme"] == "http" {
77 # capture vhost name with regex conditiona -> %0 in redirect pattern
78 # must be the most inner block to the redirect rule
79 $HTTP["host"] =~ ".*" {
80 url.redirect = (".*" => "https://%0$0")
89 \begin{lstlisting}[breaklines]
90 ssl_prefer_server_ciphers on;
91 ssl_protocols -SSLv2 -SSLv3;
92 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';
93 add_header Strict-Transport-Security max-age=2592000;
94 add_header X-Frame-Options DENY;
97 %% XXX FIXME: do we need to specify dhparams? Parameter: ssl_dhparam = file. See: http://wiki.nginx.org/HttpSslModule#ssl_protocols
100 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:
102 \begin{lstlisting}[breaklines]
103 ssl_ecdh_curve sect571k1;
106 You should redirect everything to httpS:// if possible. In Nginx you can do this with the following setting:
108 \begin{lstlisting}[breaklines]
109 rewrite ^(.*) https://$host$1 permanent;
112 %\subsubsection{openssl.conf settings}
114 %\subsubsection{Differences in SSL libraries: gnutls vs. openssl vs. others}
116 \subsubsection{MS IIS}
121 When trying to avoid RC4 and CBC (BEAST-Attack) and requiring perfect
122 forward secrecy, Microsoft Internet Information Server (IIS) supports
123 ECDSA, but does not support RSA for key exchange (consider ECC suite
124 B doubts\footnote{\url{http://safecurves.cr.yp.to/rigid.html}}).
126 Since \verb|ECDHE_RSA_*| is not supported, a SSL certificate based on
127 elliptic curves needs to be used.
129 The configuration of cipher suites MS IIS will use can be configured in one
130 of the following ways:
132 \item Group Policy \footnote{\url{http://msdn.microsoft.com/en-us/library/windows/desktop/bb870930(v=vs.85).aspx}}
134 \item IIS Crypto~\footnote{\url{https://www.nartac.com/Products/IISCrypto/}}
138 Table~\ref{tab:MS_IIS_Client_Support} shows the process of turning on
139 one algorithm after another and the effect on the supported Clients
140 tested using https://www.ssllabs.com.
142 \verb|SSL 3.0|, \verb|SSL 2.0| and \verb|MD5| are turned off.
143 \verb|TLS 1.0| and \verb|TLS 2.0| are turned on.
148 \begin{tabular}{|l|l|}
150 Cipher Suite & Client \\
152 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| & only IE 10,11, OpenSSL 1.0.1e \\
154 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| & Chrome 30, Opera 17, Safari 6+ \\
156 \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| & FF 10-24, IE 8+, Safari 5, Java 7\\
159 \caption{Client support}
160 \label{tab:MS_IIS_Client_Support}
163 Table~\ref{tab:MS_IIS_Client_Support} shows the algoriths from
164 strongest to weakest and why they need to be added in this order. For
165 example insiting on SHA-2 algorithms (only first two lines) would
166 eliminate all versions of Firefox, so the last line is needed to
167 support this browser, but should be placed at the bottom, so capable
168 browsers will choose the stronger SHA-2 algorithms.
170 \verb|TLS_RSA_WITH_RC4_128_SHA| or equivalent should also be added if
171 MS Terminal Server Connection is used (make sure to use this only in a
172 trusted environment). This suite will not be used for SSL, since we do
176 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256| ... only supported by: IE 10,11, OpenSSL 1.0.1e
177 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256| ... Chrome 30, Opera 17, Safari 6+
178 % \verb|TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA| ... Firefox 10-24, IE 8+, Safari 5, Java 7
181 Not supported Clients:
189 \subsection{Mail and POP/IMAP Servers}
190 \subsubsection{Dovecot}
196 % Example: http://dovecot.org/list/dovecot/2013-October/092999.html
198 \begin{lstlisting}[breaklines]
199 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'
200 ssl_prefer_server_ciphers = yes
203 Dovecot 2.1: Almost as good as dovecot 2.2. Does not support ssl\_prefer\_server\_ciphers
205 \paragraph*{Limitations}\mbox{}\\
207 Dovecot currently does not support disabling TLS compression. Furthermore, DH parameters
208 greater than 1024bit aren't possible. The most recent version 2.2.7 of Dovecot implements
209 configurable DH parameter length
210 \footnote{\url{http://hg.dovecot.org/dovecot-2.2/rev/43ab5abeb8f0}}.
212 \subsubsection{cyrus-imapd (based on 2.4.17)}
214 \paragraph*{imapd.conf}\mbox{}\\
216 To activate SSL/TLS configure your certificate with
217 \begin{lstlisting}[breaklines]
218 tls_cert_file: .../cert.pem
219 tls_key_file: .../cert.key
222 Do not forget to add necessary intermediate certificates to the .pem file.\\
224 Limiting the ciphers provided may force (especially older) clients to connect without encryption at all! Sticking to the defaults is recommended.\\
226 If you still want to force strong encryption use
227 \begin{lstlisting}[breaklines]
228 tls_cipher_list: <...recommended ciphersuite...>
231 cyrus-imapd loads hardcoded 1024 bit DH parameters using get\_rfc2409\_prime\_1024() by default. If you want to load your own DH parameters add them PEM encoded to the certificate file given in tls\_cert\_file. Do not forget to re-add them after updating your certificate.
233 \paragraph*{cyrus.conf}\mbox{}\\
235 To support POP3/IMAP on ports 110/143 with STARTTLS add
236 \begin{lstlisting}[breaklines]
237 imap cmd="imapd" listen="imap" prefork=3
238 pop3 cmd="pop3d" listen="pop3" prefork=1
240 to the SERVICES section.\\
242 To support POP3S/IMAPS on ports 995/993 add
243 \begin{lstlisting}[breaklines]
244 imaps cmd="imapd -s" listen="imaps" prefork=3
245 pop3s cmd="pop3d -s" listen="pop3s" prefork=1
248 \paragraph*{Limitations}\mbox{}\\
250 cyrus-imapd currently (2.4.17, trunk) does not support elliptic curves. ECDHE will not work even if defined in your cipher list.
252 Currently there is no way to prefer server ciphers or to disable compression.\\
254 There is a working patch for all three features:
255 \url{https://bugzilla.cyrusimap.org/show_bug.cgi?id=3823}\\
257 There is no way to prevent unencrypted connections on the STARTTLS ports. You can prevent usage of plaintext login by setting
258 \begin{lstlisting}[breaklines]
261 in imapd.conf. But note that SASL PLAIN/LOGIN is still available!\\
266 \todo{write this subsubsection}
268 Another option to secure IMAPs servers is to place them behind an stunnel server.
270 % XXX config von Adi?
272 % ciphers = EDH+CAMELLIA256:EDH+aRSA:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4:!SEED:-AES128:!CAMELLIA128:!ECDSA:AES256-SHA:EDH+AES128;
273 % options = CIPHER_SERVER_PREFERENCE
276 \subsubsection{Postfix}
280 First, you need to generate Diffie Hellman parameters (please first take a look at the section \ref{section:PRNG}):
282 \todo{FIXME: this is a really weak setting! See also: http://postfix.1071664.n5.nabble.com/postfix-hardening-what-can-we-do-td61874.html}
283 \begin{lstlisting}[breaklines]
284 % openssl gendh -out /etc/postfix/dh_param_512.pem -2 512
285 % openssl gendh -out /etc/postfix/dh_param_1024.pem -2 1024
288 Next, we specify these DH parameters in the postfix config file:
290 \begin{lstlisting}[breaklines]
291 smtpd_tls_dh512_param_file = /etc/postfix/dh_param_512.pem
292 smtpd_tls_dh1024_param_file = /etc/postfix/dh_param_1024.pem
295 You usually don't want restrictions on the ciphers for opportunistic
296 encryption, because any encryption is better than plain text.
298 For submission (Port 587) or other special cases, however, you want to
299 enforce strong encryption. In addition to the below entries in
300 main.cf, you need to enable ``mandatory`` encryption for the
301 respective service, e.g. by adding ``-o
302 smtpd\_tls\_security\_level=encrypt'' to the submission smtpd in
305 % don't -- this influences opportunistic encryption
306 % smtpd_tls_protocols = !SSLv2, !SSLv3
308 \begin{lstlisting}[breaklines]
309 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3
310 tls_ssl_options=NO_COMPRESSION
311 smtpd_tls_mandatory_ciphers=high
312 tls_high_cipherlist='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'
313 tls_preempt_cipherlist = yes
314 tls_random_source = dev:/dev/urandom
315 %% NOTE: might want to have /dev/random here + Haveged
318 For those users, who want to use ECC key exchange, it is possible to specify this via:
319 \begin{lstlisting}[breaklines]
320 smtpd_tls_eecdh_grade = ultra
323 You can check the settings by specifying smtpd\_tls\_loglevel = 1 and then check the selected ciphers with the following command:
324 \begin{lstlisting}[breaklines]
325 $ zegrep "TLS connection established from.*with cipher" /var/log/mail.log | \
326 > awk '{printf("%s %s %s %s\n", $12, $13, $14, $15)}' | sort | uniq -c | sort -n
327 1 SSLv3 with cipher DHE-RSA-AES256-SHA
328 23 TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384
329 60 TLSv1 with cipher ECDHE-RSA-AES256-SHA
330 270 TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
331 335 TLSv1 with cipher DHE-RSA-AES256-SHA
334 Source: \url{http://www.postfix.org/TLS_README.html}
336 \paragraph*{Limitations}\mbox{}\\
338 tls\_ssl\_options is supported from Postfix 2.11 onwards. You can
339 leave the statement in the configuration for older versions, it will
342 tls\_preempt\_cipherlist is supported from Postfix 2.8 onwards. Again,
343 you can leave the statement in for older versions.
345 \subsubsection{Exim (based on 4.82)}
347 It is highly recommended to read
349 \url{http://exim.org/exim-html-current/doc/html/spec_html/ch-encrypted_smtp_connections_using_tlsssl.html}
355 \subparagraph*{server mode (incoming)}\mbox{}\\
357 In the main config section of exim add:
359 \begin{lstlisting}[breaklines]
360 tls_certificate = ..../cert.pem
361 tls_privatekey = ..../cert.key
363 don't forget to add intermediate certificates to the .pem file if needed.\\
365 Tell exim to advertise STARTTLS in the EHLO answer:
366 \begin{lstlisting}[breaklines]
367 tls_advertise_hosts = *
370 If you want to support legacy SMTPS on port 465, and STARTTLS on smtp(25)/submission(587) ports set
371 \begin{lstlisting}[breaklines]
372 daemon_smtp_ports = smtp : smtps : submission
373 tls_on_connect_ports = 465
376 Exim already disables SSLv2 by default. We recommend to add
377 \begin{lstlisting}[breaklines]
378 openssl_options = +no_sslv2 +no_compression +cipher_server_preference
381 It is not advisable to restrict the default cipher list for opportunistic encryption as used by SMTP. Do not use cipher lists recommended for HTTPS! If you still want to define one please consult the Exim documentation or ask on the exim-users mailinglist.\\
382 % Exim maintainers do not recommend to change default ciphers
385 %\begin{lstlisting}[breaklines]
386 % tls_require_ciphers = <...recommended ciphersuite...>
389 If you want to request and verify client certificates from sending hosts set
390 \begin{lstlisting}[breaklines]
391 tls_verify_certificates = /etc/pki/tls/certs/ca-bundle.crt
392 tls_try_verify_hosts = *
395 tls\_try\_verify\_hosts only reports the result to your logfile. If you want to disconnect such clients you have to use
396 \begin{lstlisting}[breaklines]
400 You do not need to set dh\_parameters. exim with OpenSSL uses a 2048bit default prime defined in section 2.2 of RFC 5114.
401 If you want to set your own DH parameters please read the TLS documentation of exim.\\
403 The cipher used is written to the logfiles by default. You may want to add
404 \begin{lstlisting}[breaklines]
405 log_selector = <....whatever your log_selector already contains...> \
406 +tls_certificate_verified +tls_peerdn +tls_sni
408 to get even more information logged.
410 \subparagraph*{client mode (outgoing)}\mbox{}\\
412 Exim uses opportunistic encryption in the SMTP transport by default.
414 Client mode settings have to be done in the configuration section of the smtp transport (driver = smtp).
416 If you want to use a client certificate (most server certificates can be used as client certificate, too) set
417 \begin{lstlisting}[breaklines]
418 tls_certificate = .../cert.pem
419 tls_privatekey = .../cert.key
421 This is recommended for MTA-MTA traffic.\\
423 %If you want to limit used ciphers set
424 %\begin{lstlisting}[breaklines]
425 % tls_require_ciphers = <...recommended ciphersuite...>
427 % Exim Maintainers do not recommend ciphers. We shouldn't do so, too.
428 Do not limit ciphers without a very good reason. In the worst case you end up without encryption at all instead of some weak encryption. Please consult the Exim documentation if you really need to define ciphers.
430 \paragraph*{GnuTLS}\mbox{}\\
432 GnuTLS is different in only some respects to OpenSSL:
434 \item tls\_require\_ciphers needs a GnuTLS priority string instead of a cipher list. It is recommended to use the defaults by not defining this option. It highly depends on the version of GnuTLS used. Therefore it is not advisable to change the defaults.
435 \item There is no option like openssl\_options
438 \paragraph*{Limit SMTP AUTH to SSL connections only}\mbox{}\\
440 It is highly recommended to limit SMTP AUTH to SSL connections only. To do so add
441 \begin{lstlisting}[breaklines]
442 server_advertise_condition = ${if eq{$tls_cipher}{}{no}{yes}}
444 to every authenticator defined.
446 \paragraph*{Exim string expansion}\mbox{}\\
448 Note that most of the options accept expansion strings. This way you can eg. set cipher lists or STARTTLS advertisment conditionally. Please follow the link to the official Exim documentation to get more information.
450 \paragraph*{Limitations}\mbox{}\\
452 Exim currently (4.82) does not support elliptic curves with OpenSSL. This means that ECDHE is not used even if defined in your cipher list.
453 There already is a working patch to provide support:\\
454 \url{http://bugs.exim.org/show_bug.cgi?id=1397}
456 \subsubsection{SMTP: opportunistic TLS}
458 \todo{write this subsubsection}
460 Opportunistic TLS means that an MTA will accept TLS connections when asked for it durgin handshake but will not require it. One should always support incoming opportunistic TLS and alwas try TLS handshake outgoing.
463 To use outgoing opportunistic TLS in postfix
465 \begin{lstlisting}[breaklines]
466 smtp_tls_note_starttls_offer = yes¬
467 smtp_tls_security_level = may¬
471 % do we need to documment starttls in detail?
472 %\subsubsection{starttls?}
476 \begin{lstlisting}[breaklines]
478 PermitEmptyPasswords no
481 HostKey /etc/ssh/ssh_host_rsa_key
483 MACs hmac-sha2-512,hmac-sha2-256,hmac-ripemd160
484 KexAlgorithms curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
487 % XXX: curve25519-sha256@libssh.org only available upstream(!)
488 Note: older linux systems won't support SHA2, PuTTY does not support RIPE-MD160.
493 \todo{write this subsection}
494 \subsubsection{IPSec}
496 \todo{cm: check if there are downgrade attacks for checkpoint \& co} \\
497 \todo{cm: reference the paper describing how complex IPSec is and that it can't be checked properly} \\
498 \todo{cm: change this to a table format: Variant ((A,B), (recommendations, recommendations))} \\
500 \paragraph*{Assumptions}\mbox{}\\
502 We assume the usage of IKE (v1 or v2) for this document, and ESP.
504 \paragraph*{Authentication}\mbox{}\\
506 IPSEC authentication should optimally be performed via RSA signatures,
507 with a key size of 2048 bits or more. Configuring only the trusted CA
508 that issued the peer certificate provides for additional protection
509 against fake certificates.
511 If you need to use Pre-Shared Key authentication:
514 \item Choose a \textbf{random} PSK of 20 characters or more (\todo{length, references!})
515 \item Use a \textbf{separate} PSK for any IPSEC connection
516 \item Change the PSKs regularily
519 \paragraph*{Cryptographic Suites}\mbox{}\\
521 IPSEC Cryptographic Suites are pre-defined settings for all the
522 items of a configuration; they try to provide a balanced security
523 level and make setting up VPNs easier.
525 When using any of those suites, make sure to enable ``Perfect Forward
526 Secrecy`` for Phase 2, as this is not specified in the suites.
528 \verb|Suite-B-GCM-256| \footnote{\url{http://tools.ietf.org/html/rfc6379}}
529 would be roughly equivalent to ``Configuration A``, but keep in mind
530 that it uses NIST elliptic curves for the Diffie-Hellman key exchange.
532 \verb|Suite-B-GCM-128| or
533 \verb|VPN-B| \footnote{\url{http://tools.ietf.org/html/rfc4308}} would
534 be roughly equivalent to ``Configuration B``; again,
535 \verb|Suite-B-GCM-128| uses NIST elliptic curves, \verb|VPN-B| does
538 \todo{Aaron: make an example for how to include images}
539 \todo{cm: screenshots of Checkpoint settings}
541 \paragraph*{IKE or Phase 1}\mbox{}\\
543 IKE or Phase 1 is the mutual authentication and key exchange phase.
545 Use only ``main mode``, as ``aggressive mode`` has known security
546 vulnerabilities \footnote{\url{http://ikecrack.sourceforge.net/}}.
548 Encryption Algorithm: AES or CAMELLIA
550 Hash Algorithm: SHA2-256, SHA2-384 or SHA2-512
552 DH Group: Group 14--18 (2048--8192 bit DH), or 19-21 (256--521 bit
555 Lifetime: \todo{need recommendations; 1 day seems to be common practice}
557 \todo{what about CAST?}
559 \paragraph*{ESP or Phase 2}\mbox{}\\
561 Enable ``Perfect Forward Secrecy`` with a DH Group equivalent to the
564 Encryption Algorithm: AES-GCM-16, AES-CTR, AES-CCM-16, AES-CBC, SEED
565 or CAMELLIA \todo{order of this list?}
567 Hash Algorithm: none (if using AES-GCM), HMAC-SHA-SHA256 or longer
568 \todo{what about AES-XCBC-MAC?}
570 Lifetime: \todo{need recommendations; 1--8 hours seems to be common practice}
573 \subsubsection{OpenVPN}
574 \todo{cm: please write this subsubsection}
575 \todo{WARNING - Section Writing in progress...}
576 \todo{We suppose user uses easy-rsa which is roughly used in all HOWTO}
578 \paragraph{Fine tuning at installation level}
580 When installing an OpenVPN server instance, you are probably using \it{easy-rsa} tools to generate the crypto stuff needed.
581 From the directory where you will run them, you can enhanced you configuration by changing the following variables in \it{Vars}
583 \begin{lstlisting}[breaklines]
587 This will enhanced the security of the key exchange steps by using RSA keys with a length of 2048 bits.
589 \todo{Shouldn't we need to reduce CA and certificate lifetime? Per default 10y!!}
592 \paragraph{Server Configuration}
594 \todo{To wrote - locked by David}
596 \begin{lstlisting}[breaklines]
597 cipher AES-128-CBC # AES
601 \paragraph{Client Configuration}
603 \todo{To wrote - locked by David}
605 \begin{lstlisting}[breaklines]
612 \todo{cm: please write this subsubsection}
614 \subsubsection{Cisco IPSec}
615 \todo{write this subsubsection}
617 \subsubsection{Juniper VPN}
618 \todo{write this subsubsection. AK: ask Hannes}
620 \subsubsection{L2TP over IPSec}
621 \todo{write this subsubsection}
623 \subsubsection{Racoon}
624 \todo{write this subsubsection}
627 \subsection{PGP/ GPG - Pretty Good Privacy}
629 \todo{re-work this subsection -- this is still only a draft!!}
632 \subsection{seclayer-tcp}
633 \todo{Ramin: please write this section or ask Posch}
634 For the austrian citizen card....
637 seclayer-tcp 3495/udp # securitylayer over tcp
638 seclayer-tcp 3495/tcp # securitylayer over tcp
642 \subsection{IPMI, ILO and other lights out management solutions}
643 \todo{write this!! Recommendation. Empfehlung: nie ins Internet, nur in ein eigenes mgmt VLAN, das via VPN erreichbar ist!!
647 \todo{AK: ask Klaus. Write this section, Klaus??? }
649 \subsection{Instant Messaging Systems}
650 \subsubsection{XMPP / Jabber}
653 %\subsection{Database Systems}
654 %\subsubsection{MySQL}
656 %\paragraph*{my.cnf}\mbox{}\\
658 %%Tested with Debian 7.0 and MySQL 5.5
660 %\begin{lstlisting}[breaklines]
663 %ssl-ca=/etc/mysql/ssl/ca-cert.pem
664 %ssl-cert=/etc/mysql/ssl/client-cert.pem
665 %ssl-key=/etc/mysql/ssl/client-key.pem
666 %ssl-cipher=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
669 %After restarting the server run the following query to see if the ssl settings are correct:
670 %\begin{lstlisting}[breaklines]
671 %show variables like '%ssl%';
678 %%% TeX-master: "applied-crypto-hardening"