[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[freehaven-cvs] one fix and one potential fix (?)
Update of /home/freehaven/cvsroot/doc/sync-batching
In directory moria.mit.edu:/home2/arma/work/freehaven/doc/sync-batching
Modified Files:
sync-batching.tex
Log Message:
one fix and one potential fix (?)
Index: sync-batching.tex
===================================================================
RCS file: /home/freehaven/cvsroot/doc/sync-batching/sync-batching.tex,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -d -r1.51 -r1.52
--- sync-batching.tex 27 Jan 2004 15:43:19 -0000 1.51
+++ sync-batching.tex 11 Apr 2004 06:57:51 -0000 1.52
@@ -161,7 +161,7 @@
exponentially with $t$, then so does the probability that
a message leaving the network could have been sent that long
ago~\cite{Serj02}.)
-Also, because Mixmaster is both {\em asynchronous} (messages can enter
+Also, because Mixminion is both {\em asynchronous} (messages can enter
and leave the network at any time) and uses free routes, it is subject
to the attacks from~\cite{disad-free-routes} described in
Section~\ref{subsec:disad} below.
@@ -260,6 +260,7 @@
%long as they use synchronous batching, they are not vulnerable to this
%particular attack.}
+% XXX I think we mean 'unlinkability' here? -RD
{\bf{Probability of Unobservability:}} The authors explain that the
cascade topology optimizes for the case that only one mix node is
honest. They compare a 4-node cascade (with 3 compromised nodes) to
***********************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe freehaven-cvs in the body. http://freehaven.net/