summaryrefslogtreecommitdiff
path: root/doc/paper/taler_FC2017.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/paper/taler_FC2017.txt')
-rw-r--r--doc/paper/taler_FC2017.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/paper/taler_FC2017.txt b/doc/paper/taler_FC2017.txt
index de1c64a30..66f8560ad 100644
--- a/doc/paper/taler_FC2017.txt
+++ b/doc/paper/taler_FC2017.txt
@@ -21,7 +21,7 @@ be insecure.
> We added a section with proofs
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
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