proxy solutions: deleted repeating text

mailservers: formatting
im: it was not clear where the version string starts and ends

diff --git a/src/practical_settings/im.tex b/src/practical_settings/im.tex
index 25b3c32..2ee2f75 100644 (file)
--- a/src/practical_settings/im.tex
+++ b/src/practical_settings/im.tex
@@ -18,7 +18,7 @@ The last point being out-of-scope for this section, we will only cover the first
 \paragraph{ejabberd}
 
 \begin{description}
-\item[Tested with Version:] Debian 7.0 2.1.10-4+deb7u1
+\item[Tested with Version:] Debian 7.0, version 2.1.10-4+deb7u1
 
 \item[Settings:] \mbox{}
 

diff --git a/src/practical_settings/mailserver.tex b/src/practical_settings/mailserver.tex
index 8161c4f..d1b0b17 100644 (file)
--- a/src/practical_settings/mailserver.tex
+++ b/src/practical_settings/mailserver.tex
@@ -342,7 +342,7 @@ It is not advisable to restrict the default cipher list for MSA mode if you don'
 
 The cipher used is written to the logfiles by default. You may want to add
 \begin{lstlisting}[breaklines]
-  log_selector = <....whatever your log_selector already contains...> \
+  log_selector = <whatever your log_selector already contains> \
    +tls_certificate_verified +tls_peerdn +tls_sni
 \end{lstlisting}
 to get even more TLS information logged.
@@ -389,7 +389,7 @@ tls\_try\_verify\_hosts only reports the result to your logfile. If you want to
 
 The cipher used is written to the logfiles by default. You may want to add
 \begin{lstlisting}[breaklines]
-  log_selector = <....whatever your log_selector already contains...> \
+  log_selector = <whatever your log_selector already contains> \
    +tls_certificate_verified +tls_peerdn +tls_sni
 \end{lstlisting}
 to get even more TLS information logged.

diff --git a/src/practical_settings/proxy_solutions.tex b/src/practical_settings/proxy_solutions.tex
index b686232..425a81d 100644 (file)
--- a/src/practical_settings/proxy_solutions.tex
+++ b/src/practical_settings/proxy_solutions.tex
@@ -23,7 +23,6 @@ Conclusion: Don't forget to check your proxy solutions SSL-capabilities. Also do
 As of squid-3.2.7 (01 Feb 2013) there is support for the OpenSSL NO\_Compression option within squid config (CRIME attack) and if you combine that in the config file, with an enforcement of the server cipher preferences (BEAST Attack) you are safe.
 
 \paragraph*{squid.conf}\mbox{}\\
-squid.conf
 
 \todo{UNTESTED!}
 \begin{lstlisting}[breaklines]
@@ -34,7 +33,6 @@ cipher=@@@CIPHERSTRINGB@@@
 
 
 \paragraph*{squid.conf}\mbox{}\\
-squid.conf
 
 %% http://forum.pfsense.org/index.php?topic=63262.0