gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-marketing] branch master updated: more refs


From: gnunet
Subject: [taler-marketing] branch master updated: more refs
Date: Thu, 27 Jan 2022 19:29:19 +0100

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 5a42722  more refs
5a42722 is described below

commit 5a4272207d3d4fc198187d33bacb0d10824e3f8d
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Thu Jan 27 19:29:16 2022 +0100

    more refs
---
 2022-privacy/cwps.pdf       | Bin 0 -> 28621 bytes
 2022-privacy/lightening.pdf | Bin 0 -> 1759778 bytes
 2022-privacy/literature.bib |  96 +++++++++++++++++++++++++++++++++++++++++++-
 2022-privacy/privacy.tex    |  11 +++--
 4 files changed, 99 insertions(+), 8 deletions(-)

diff --git a/2022-privacy/cwps.pdf b/2022-privacy/cwps.pdf
new file mode 100644
index 0000000..76e1aaf
Binary files /dev/null and b/2022-privacy/cwps.pdf differ
diff --git a/2022-privacy/lightening.pdf b/2022-privacy/lightening.pdf
new file mode 100644
index 0000000..92e7549
Binary files /dev/null and b/2022-privacy/lightening.pdf differ
diff --git a/2022-privacy/literature.bib b/2022-privacy/literature.bib
index ec6b004..8e2ccea 100644
--- a/2022-privacy/literature.bib
+++ b/2022-privacy/literature.bib
@@ -1,10 +1,104 @@
 @misc{schneier2016toxic,
+  author = {Bruce Schneier},
   title = {Data Is a Toxic Asset, So Why Not Throw It Out?},
   year = {2016},
   month = {March},
   howpublished = 
{\url{https://www.schneier.com/essays/archives/2016/03/data_is_a_toxic_asse.html}},
 }
 
+@PhdThesis{cwps,
+  author =       {J. Appelbaum},
+  title =        {Communication in a world of pervasive surveillance},
+  school =       {TU Eindhoven},
+  year =         {2022},
+  month =     {February},
+}
+
+@misc{zcash,
+  title={Zcash protocol specification},
+  author={Hopwood, Daira and Bowe, Sean and Hornby, Taylor and Wilcox, Nathan},
+  
howpublished={\url{https://raw.githubusercontent.com/zcash/zips/master/protocol/protocol.pdf}},
+  year={2016}
+}
+
+@book{voigt2017eu,
+  title={The EU General Data Protection Regulation (GDPR)},
+  author={Voigt, Paul and Von dem Bussche, Axel},
+  volume={18},
+  year={2017},
+  publisher={Springer}
+}
+@article{lightening,
+       doi = {10.1088/1367-2630/aba062},
+       url = {https://doi.org/10.1088/1367-2630/aba062},
+       year = 2020,
+       month = {aug},
+       publisher = {{IOP} Publishing},
+       volume = {22},
+       number = {8},
+       pages = {083022},
+       author = {Jian-Hong Lin and Kevin Primicerio and Tiziano Squartini and 
Christian Decker and Claudio J Tessone},
+       title = {Lightning network: a second path towards centralisation of the 
Bitcoin economy},
+       journal = {New Journal of Physics},
+}
+@InCollection{ chaum2021,
+  author =       {David Chaum and Christian Grothoff and Thomas Moser},
+  title =        {How to Issue a Central Bank Digital Currency},
+  booktitle =    {SNB Working Papers},
+  publisher =    {Swiss National Bank},
+  year =         {2021},
+  number =       {2021-3},
+  month =        {February},
+}
+
+@Misc{p2e2022,
+  author =    {Paul Butler},
+  title =     {"Play-to-earn” and Bullshit Jobs},
+  howpublished = 
{\url{https://paulbutler.org/2021/play-to-earn-and-bullshit-jobs/}},
+  month =     {December},
+  year =      {2021},
+}
+
+@inproceedings{sahin2010overview,
+  title={An overview of business domains where fraud can take place, and a 
survey of various fraud detection techniques},
+  author={Sahin, Y and Duman, E},
+  booktitle={Proceedings of the 1st international symposium on computing in 
science and engineering, Aydin, Turkey},
+  year={2010}
+}
+@inproceedings{garera2007framework,
+  title={A framework for detection and measurement of phishing attacks},
+  author={Garera, Sujata and Provos, Niels and Chew, Monica and Rubin, Aviel 
D},
+  booktitle={Proceedings of the 2007 ACM workshop on Recurring malcode},
+  pages={1--8},
+  year={2007},
+  organization={ACM}
+}
+@book{stallman2002essays,
+  title={Free software, free society: Selected essays of Richard M. Stallman},
+  author={Stallman, Richard},
+  year={2002},
+  publisher={Lulu.com}
+}
+
+@inproceedings{monero,
+  title={RingCT 2.0: a compact accumulator-based (linkable ring signature) 
protocol for blockchain cryptocurrency monero},
+  author={Sun, Shi-Feng and Au, Man Ho and Liu, Joseph K and Yuen, Tsz Hon},
+  booktitle={European Symposium on Research in Computer Security},
+  pages={456--474},
+  year={2017},
+  organization={Springer}
+}
+
+
+@Misc{afganistan2021,
+  author =    {Margaret Hu},
+  title =     {The Taliban reportedly have control of US
+biometric devices -- a lesson in life-and-death consequences
+of data privacy},
+  howpublished = 
{\url{https://theconversation.com/the-taliban-reportedly-have-control-of-us-biometric-devices}},
+  year =      {2021},
+}
+
 @TechReport{usfed2022,
   author =       {{Board of Governers of the Federal Reserve System}},
   title =        {{Money and Payments: The U.S. Digital Dollar in the Age of 
Digital Transformation}},
@@ -51,7 +145,6 @@
 
 @Inbook{Helbing2019,
 author="Helbing, Dirk",
-editor="Helbing, Dirk",
 title="Digital Fascism Rising?",
 bookTitle="Towards Digital Enlightenment: Essays on the Dark and Light Sides 
of the Digital Revolution",
 year="2019",
@@ -449,4 +542,3 @@ series = {SEC'16}
   year         = 2020,
   month        = {December}
 }
-
diff --git a/2022-privacy/privacy.tex b/2022-privacy/privacy.tex
index 065002d..22691cf 100644
--- a/2022-privacy/privacy.tex
+++ b/2022-privacy/privacy.tex
@@ -573,7 +573,7 @@ inspired by~\cite{dold2019}, given in order of priority:
 \end{enumerate}
 
 In our opinion, any candidate for CBDC must follow at least those principles
-to be trustworthy and successful.  
+to be trustworthy and successful.
 
 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
@@ -581,11 +581,11 @@ designs always strive to avoid trusted parties. This 
implies that neither the
 correctness nor the privacy assurances must rely on an honest central
 bank. Michael Hayden (the former head of the CIA and NSA) famously made the
 mistake of asserting that with respect to control over the toxic data assets
-accumulated by the NSA ``nobody comes after us''~\cite{jake2022}, suggesting
+accumulated by the NSA ``nobody comes after us''~\cite[page 6f]{cwps}, 
suggesting
 that the (by Mr. Hayden presumed trustworthy) US government would never
 fall. This false assumption quickly 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{afganistan2022}.  We
+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
 good and eternal, when it comes to out private payment data. Thus, it is
 necessary that technical protections for our privacy are put in place that
@@ -672,7 +672,8 @@ control.
 
 There are no trusted third parties. That does not prevent people from
 designing and deploying systems that rely on the assumption that a trusted
-third party exists. Central banks must not follow Michael Hayden's hybris
+third party exists. Central banks must not follow Michael Hayden's
+hybris~\cite[page 6f]{cwps}
 and assert that they are an eternally trusted third party.
 
 The dominance of accounts on the Internet and the resulting delegation of
@@ -735,5 +736,3 @@ directly, transactions using real coins and bills are 
declining. The quantity
 of money, as well as the interest rate at which this money is made available
 to banks, allows central banks to influence the value of the currencies they
 manage.
-
-

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]