# HG changeset patch
# User Christian Urban <urbanc@in.tum.de>
# Date 1350985140 -3600
# Node ID 6c81e42e539d9ccad80440c627912d4e8f6b9925
# Parent  be19f8a1fcf07844c5bab405646373feec156ad8
tuned

diff -r be19f8a1fcf0 -r 6c81e42e539d slides05.pdf
Binary file slides05.pdf has changed
diff -r be19f8a1fcf0 -r 6c81e42e539d slides05.tex
--- a/slides05.tex	Tue Oct 23 00:30:45 2012 +0100
+++ b/slides05.tex	Tue Oct 23 10:39:00 2012 +0100
@@ -183,7 +183,7 @@
   \draw[red,<-, line width = 2mm] (-0.6,1) -- (-1.6,1);
   \draw[red, <-, line width = 3mm] (0.6,2.2) -- (0.6,3.2); 
   
-  \draw (0.6,4) node {\begin{tabular}{l}\large Some Rules\\(access policy)\end{tabular}};
+  \draw (0.6,4) node {\begin{tabular}{l}\large some rules\\(access policy)\end{tabular}};
 
   \end{tikzpicture}
 \end{center}
@@ -202,7 +202,7 @@
 \begin{quote}
 Formal methods can be an excellent way of finding 
 bugs in security protocol designs as they force the designer 
-to make everything explicit and thus confront difficult design 
+to make everything explicit and thus confront dif$\!$ficult design 
 choices that might otherwise be fudged. 
 \end{quote}
 
@@ -225,7 +225,7 @@
   \draw[red,<-, line width = 2mm] (-0.6,1) -- (-1.6,1);
   \draw[red, <-, line width = 3mm] (0.6,2.2) -- (0.6,3.2); 
   
-  \draw (0.6,3.7) node {\begin{tabular}{l}Access Policy\end{tabular}};
+  \draw (0.6,3.7) node {\begin{tabular}{l}access policy\end{tabular}};
 
   \end{tikzpicture}
 \end{center}
@@ -1234,6 +1234,21 @@
   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 %
 
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\mode<presentation>{
+\begin{frame}[c]
+\frametitle{Point to Take Home}
+
+\begin{itemize}
+\item Formal methods can be an excellent way of finding 
+bugs as they force the designer 
+to make everything explicit and thus confront dif$\!$ficult design 
+choices that might otherwise be fudged. 
+\end{itemize}
+
+\end{frame}}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%   
+
 
 
 \end{document}