inline FC reviews/responses in main paper
This commit is contained in:
parent
998858bc8f
commit
57fef70492
@ -58,7 +58,8 @@
|
|||||||
\usetikzlibrary{calc}
|
\usetikzlibrary{calc}
|
||||||
\usepackage{eurosym}
|
\usepackage{eurosym}
|
||||||
\usepackage[T1]{fontenc}
|
\usepackage[T1]{fontenc}
|
||||||
|
\usepackage{verbatim}
|
||||||
|
\usepackage[utf8]{inputenc}
|
||||||
|
|
||||||
% Copyright
|
% Copyright
|
||||||
%\setcopyright{none}
|
%\setcopyright{none}
|
||||||
@ -1868,6 +1869,16 @@ data being persisted are represented in between $\langle\rangle$.
|
|||||||
\item[$\overline{C^{(i)}_p}$]{Public coin keys computed from $\overline{c_s^{(i)}}$ by the verifier}
|
\item[$\overline{C^{(i)}_p}$]{Public coin keys computed from $\overline{c_s^{(i)}}$ by the verifier}
|
||||||
\end{description}
|
\end{description}
|
||||||
|
|
||||||
|
\newpage
|
||||||
|
\onecolumn
|
||||||
|
\section{Supplemental: Reviews and Responses from Financial Cryptography}
|
||||||
|
|
||||||
|
\subsection{FC 2016}
|
||||||
|
\verbatiminput{taler_FC2016.txt}
|
||||||
|
|
||||||
|
\subsection{FC 2017}
|
||||||
|
\verbatiminput{taler_FC2017.txt}
|
||||||
|
|
||||||
\end{document}
|
\end{document}
|
||||||
|
|
||||||
|
|
||||||
|
@ -21,7 +21,7 @@ be insecure.
|
|||||||
> We added a section with proofs
|
> We added a section with proofs
|
||||||
|
|
||||||
I find two (possible) attacks against the refresh protocol. As the
|
I find two (possible) attacks against the refresh protocol. As the
|
||||||
exchange does not check the validity of the public key Cp′ , the attacker can
|
exchange does not check the validity of the public key Cp', the attacker can
|
||||||
send an arbitrary public key to the exchange that will accept, and obtain a
|
send an arbitrary public key to the exchange that will accept, and obtain a
|
||||||
fresh coin. The attacker can spend partially a coin multiple times via
|
fresh coin. The attacker can spend partially a coin multiple times via
|
||||||
refreshing the coin and obtaining a fresh coin in turn, as the refresh protocol
|
refreshing the coin and obtaining a fresh coin in turn, as the refresh protocol
|
||||||
|
Loading…
Reference in New Issue
Block a user