[taler-marketing] branch master updated: integrate Martin feedback

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new c61823f  integrate Martin feedback
c61823f is described below

commit c61823f7e60fef66aa1c941f1d63956203717f83
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sun Apr 24 22:32:26 2022 +0200

    integrate Martin feedback
---
 2022-privacy/slides.tex | 90 +++++++++++++++++--------------------------------
 1 file changed, 30 insertions(+), 60 deletions(-)

diff --git a/2022-privacy/slides.tex b/2022-privacy/slides.tex
index 2997c86..5470ffe 100644
--- a/2022-privacy/slides.tex
+++ b/2022-privacy/slides.tex
@@ -81,51 +81,12 @@ C.~Grothoff, \"O.~Kesim \& M.~Schanzenbach
 \end{frame}
 
 
-\begin{frame}{Principles for Secure System Design}
-  \begin{itemize}
-  \item Kerkhoff's principle: {\bf Security should not depend upon the secrecy 
of design (or mechanism).}
-  \item Economy of mechanism: {\bf Prefer mechanisms that are simpler and 
smaller.}
-  \item Least privilege: {\bf A principal should have the minimum privileges 
it needs to accomplish its desired operations.}
-  \item Limit trust: {\bf Trust should not be granted forever.}
-  \item Minimized sharing: {\bf No resource should be shared between 
components or subjects unless it is necessary to
-    do so.}
-  \item Inverse modification threshold: {\bf The degree of protection provided 
to a component must be commensurate with its trustworthiness.}
-  \item Acceptable security: {\bf The level of privacy the system provides 
should be consistent with the users’ expectations.}
-  \end{itemize}
-  \begin{center}
-    ``Important principles may, and must, be inflexible.'' --Abraham Lincoln
-  \end{center}
-\end{frame}
-
-
 \begin{frame}{How much trust and protection are needed?}
     \includegraphics[width=0.45\textwidth]{twitter.jpg}
     \includegraphics[width=0.45\textwidth]{twitter2.jpg}
 \end{frame}
 
 
-\begin{frame}{Hacker Ethics --- by Levy}
-  \begin{itemize}
-  \item Access to anything which might teach you something about the way the 
world works should be unlimited and total.
-  \item Mistrust authority.
-  \item Hackers should be judged by their hacking, not bogus criteria such as 
degrees, age, race, sex, {\bf or position}.
-  \end{itemize} \pause
-  \begin{center}
-     {\bf This excludes soliciting advice only from companies with 100 million 
EUR in annual turnover.}
-  \end{center}
-\end{frame}
-
-
-\section{Solution}
-\begin{frame}{The Right Mindset\footnote{Image: That Mitchell and Webb Look: 
Series 1 Episode 1}}
-\vfill
-  \begin{center}
-    \includegraphics[width=0.7\textwidth]{are-we-the-baddies.jpg}
-  \end{center}
-\vfill
-\end{frame}
-
-
 \begin{frame}{GDPR principles}
   \begin{itemize}
   \item Lawfulness, fairness and transparency
@@ -143,20 +104,35 @@ C.~Grothoff, \"O.~Kesim \& M.~Schanzenbach
 \end{frame}
 
 
-\begin{frame}{Blockchain-based designs with accounts}
+\begin{frame}{Designs with accounts}
   \begin{itemize}
   \item Lawfulness?, fairness and transparency
   \item \sout{Purpose limitation}
   \item \sout{Data minimisation}
   \item Accuracy?
-  \item \sout{Storage limitation}
+  \item Storage limitation?
   \item Integrity and \sout{confidentiality (security)}
   \item Accountability
   \end{itemize}
+  \begin{center}
+  ``Data is a toxic asset.'' --Bruce Schneier
+  \end{center}
   \vfill
 \end{frame}
 
 
+\end{document}
+
+\section{Solution}
+\begin{frame}{The Right Mindset\footnote{Image: That Mitchell and Webb Look: 
Series 1 Episode 1}}
+\vfill
+  \begin{center}
+    \includegraphics[width=0.7\textwidth]{are-we-the-baddies.jpg}
+  \end{center}
+\vfill
+\end{frame}
+
+
 \begin{frame}{Meta Problems}
   \begin{itemize}
   \item Meta proposed that for Libra/Diem they would ``firewall'' the Facebook 
profile data
@@ -172,25 +148,19 @@ C.~Grothoff, \"O.~Kesim \& M.~Schanzenbach
 \end{frame}
 
 
-\begin{frame}{Past, Present and Future}
-Past:
-  \begin{itemize}
-  \item Designed and implemented ethical and scalable rCBDC
-  \item Prepared extensive report on payments for German parliament
-  \item Advised over a dozen central banks about rCBDC for free
-  \end{itemize}\pause
-Present:
-  \begin{itemize}
-  \item Prepared submission for Digital Euro consultation
-  \item Tried to collaborate with large firms
-  \item Large firms gained business intelligence, applied without us
-  \end{itemize}\pause
-Future:
+
+\begin{frame}{Principles for Secure System Design}
   \begin{itemize}
-  \item How can we help you prevent a Chinese-style ``anonymous'' rCBDC
-        in a way that does not require a tender procurement process?
+  \item Kerkhoff's principle: {\bf Security should not depend upon the secrecy 
of design (or mechanism).}
+  \item Economy of mechanism: {\bf Prefer mechanisms that are simpler and 
smaller.}
+  \item Least privilege: {\bf A principal should have the minimum privileges 
it needs to accomplish its desired operations.}
+  \item Limit trust: {\bf Trust should not be granted forever.}
+  \item Minimized sharing: {\bf No resource should be shared between 
components or subjects unless it is necessary to
+    do so.}
+  \item Inverse modification threshold: {\bf The degree of protection provided 
to a component must be commensurate with its trustworthiness.}
+  \item Acceptable security: {\bf The level of privacy the system provides 
should be consistent with the users’ expectations.}
   \end{itemize}
+  \begin{center}
+    ``Important principles may, and must, be inflexible.'' --Abraham Lincoln
+  \end{center}
 \end{frame}
-
-
-\end{document}

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.