aboutsummaryrefslogtreecommitdiff
path: root/slides/2021-pets/src/end.tex
diff options
context:
space:
mode:
Diffstat (limited to 'slides/2021-pets/src/end.tex')
-rw-r--r--slides/2021-pets/src/end.tex34
1 files changed, 34 insertions, 0 deletions
diff --git a/slides/2021-pets/src/end.tex b/slides/2021-pets/src/end.tex
new file mode 100644
index 0000000..56beaf3
--- /dev/null
+++ b/slides/2021-pets/src/end.tex
@@ -0,0 +1,34 @@
+\begin{frame}
+ %
+ % As a take away I hope that you are convinced that Tor Browser would
+ % benefit from CT.
+ % - This was the first part of the presentation.
+ %
+ % CT would also benefit from more auditing, which we can do here in a secure
+ % and privacy-preserving manner because of and how we use Tor.
+ % - This was the second part of the presentation.
+ %
+ % Although not presented here, we show in our paper that the resulting
+ % system is also performant based on estimations from two public data sets.
+ %
+ % An important insight from our work is that pushing the auditing logic
+ % away from Tor Browser is important to defend against relevant threats.
+ % The simple approach of "just fetching an inclusion proof" does not work.
+ %
+ % That's it. Thanks!
+ \vfill
+ \begin{columns}
+ \begin{column}{0.6\textwidth}
+ \mktitle{Take away}
+ \begin{itemize}
+ \item Tor Browser would benefit from CT
+ \item CT would benefit from more auditing
+ \item Delegated auditing is key in our setting
+ \end{itemize}
+ \end{column}
+ \begin{column}{0.4\textwidth}
+ \centering
+ \includegraphics[width=.8\columnwidth]{img/thanks}
+ \end{column}
+ \end{columns}
+\end{frame}