commit 2d586609ec732bec9cbe147aab443b1a46c8c69e
parent 7dfee4188839870d6cf446c2a5eaaef373bb97d6
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Fri, 28 Jan 2022 09:39:41 +0100
wording
Diffstat:
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/2022-privacy/privacy.tex b/2022-privacy/privacy.tex
@@ -579,11 +579,12 @@ A cross-cutting concern here is that when achieving the security goals, the
CBDC must never rely on the central bank being trustworthy. Good security
designs always strive to avoid trusted parties. This implies that neither the
correctness nor the privacy assurances must rely on an honest central
-bank. The former director of the NSA made the
-mistake of asserting that with respect to control over the toxic data assets
+bank.
+This false sense of security also became evident when the former director of the
+NSA made revealed his belief that with respect to control over the toxic data assets
accumulated by the NSA ``nobody comes after us''~\cite[page 6f]{cwps}, suggesting
that the (by the DIRNSA clearly presumed trustworthy) US government would never
-fall. This false assumption quickly turned deadly when the Taliban took over
+fall. The assumption turned deadly when the Taliban took over
personal profiles including biometric data of Afgahnis that had collaborated
with NATO forces after the retreat of NATO in 2021~\cite{afganistan2021}. We
must not make the same mistake, that is believing that our institutions are