[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[freehaven-cvs] Fixed revpar, abstract and intro.



Update of /home2/freehaven/cvsroot/doc/pingers
In directory moria:/tmp/cvs-serv32479

Modified Files:
	pingers.tex 
Log Message:
Fixed revpar, abstract and intro.


Index: pingers.tex
===================================================================
RCS file: /home2/freehaven/cvsroot/doc/pingers/pingers.tex,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- pingers.tex	10 Mar 2006 03:58:40 -0000	1.7
+++ pingers.tex	10 Mar 2006 20:06:32 -0000	1.8
@@ -11,17 +11,34 @@
 \small
 }
 {\end{figure}
-%\renewcommand{\baselinestretch}{2}
+\renewcommand{\baselinestretch}{2}
 }
 % replace bullets by dashes in itemize
 \renewcommand\labelitemi{\normalfont\bfseries --}
 \renewcommand\labelitemii{$\m@th\bullet$}
 
+\newenvironment{revpar}{%
+\begin{list}%
+{}{\setlength{\labelwidth}{0in}%
+\setlength{\itemsep}{0in}%
+\setlength{\topsep}{0in}%
+\setlength{\leftmargin}{4em}%
+\setlength{\itemindent}{-2em}}}{\end{list}}
+
+\newenvironment{algorithm}{%
+\medbreak%
+\begin{list}%
+{}{\setlength{\labelwidth}{0in}%
+\setlength{\listparindent}{0in}%
+\setlength{\rightmargin}{0in}} \small \item}{\end{list}}
+
+
 \title{Echolot and Leuchtfeuer: Measuring the Reliability of Unreliable Mixes}
 
 % Blinded for submission
 
-%\author{Len Sassaman\inst{1} and Klaus Kursawe\inst{1} and Peter Palfrader\inst{2}
+%\author {Klaus Kursawe\inst{1} and Peter Palfrader\inst{2} and Len Sassaman\inst{1}
+
 
 %foo
 %\institute{Katholieke Universiteit Leuven\\
@@ -44,38 +61,55 @@
 
 \begin{abstract}
 
-In a network of distributed mix-net servers, information regarding the
-network health and operational behavior of the individual nodes must be
-made available to the client applications, to select reliable nodes to use
-in each message's path through the mix-network. We present a summary of
-the techniques currently in use, and evaluate their methods.
+In a mix-net, information regarding the network health and operational
+behavior of the individual nodes must be made available to the client
+applications so they may select reliable nodes to use in each message's
+path through the mix-network.
 
 We evaluate the security concerns regarding an information service,
 including the issues regarding anonymity set preservation, information
 disclosure, and node cheating.
 
+We present \emph{Echolot},the most advanced remailer reliability
+monitoring software and \emph{Leuchtfeuer}, a protocol enhancement for
+mix-networks which solves a serious security vulnerability.
+
 \end{abstract}
 
 
 \section{Introduction}
 
 Chaum~\cite{chaum-1981} introduced the concept of mixes as a method of
-providing secure anonymous communication. The publicly accessible mix
-networks~\cite{}, operated by volunteers, are prone to intermittent
-failure of individual nodes. It is therefore necessary for mix client
-software to have an accurate view of the health of the nodes in the mix
-network. This information is gathered by sending test messages through
-each node, and observing the success or failure of the mix to successfully
-transmit the message. In a similar fashion, links between mixes are
-examined by sending messages through every combination of two consequtive
-mixes. Since the overhead and operational complexity involved in
-monitoring an entire network of mixes is too great for the average user,
-\emph{pingers} perform this function, and provide their results for
-download by the mix clients. Pingers track additional information as well,
-such as the average latency provided by each mix, changes in the key
-information and capabilities of the mixes, and so forth.
+providing secure anonymous network communication. The publicly accessible
+mix networks, such as the ``Type I'' Cypherpunk remailers, the ``Type II''
+Mixmaster network, and the ``Type III'' Mixminion network~\cite{}, as well
+as the low-latency network anonymity service Tor are operated by
+volunteers and are prone to intermittent failure of individual nodes. It
+is therefore necessary for mix client software to have an accurate view of
+the health of the nodes in the mix network. This information is gathered
+by sending test messages through each node, and observing the success or
+failure of the mix to successfully transmit the message. In a similar
+fashion, links between mixes are examined by sending messages through
+every combination of two consecutive mixes. Since the overhead and
+operational complexity involved in monitoring an entire network of mixes
+is too great for the average user, reliability testing servers, or
+\emph{pingers}, perform this function and publish their results in a
+machine-parsable format. The results are downloaded and interpretted by
+the mix clients. Pingers track additional information as well, such as the
+average latency provided by each mix, changes in the key information and
+capabilities of the mixes, and so forth.
 
-\section{Prior work}
+In this paper we give an overview of the different pinger systems that
+have been developed for the Mixmaster network, and describe the problems
+they attempt to address, as well as their relative success at doing so. We
+present Echolot, our pinger implementation which more adequately addresses
+the problem of reliability monitoring than the other pingers. Finally, we
+explain the problem of pinger inconsistency, an issue which poses
+significant security implications and is shared by all existing pingers
+and mix clients. To solve this, we present the pinger agreement protocol
+Leuchtfeuer.
+
+\section{Related work}
 \label{pingers}
 
 \subsection{rlist}
@@ -95,10 +129,9 @@
 %   so a remailer can't just make up pings if me missed a few
 % http://ixazon.dynip.com/~cmeclax/pingstats.html   FIXME, please add bibitem
 
-Pingstats\cite{pingstats}, developed by cmeclax between 2000 and 2003 is
-a pinger written in C and shell scripts that are executed from Cron, a
-Unix daemon that executes programs at previously specified times.
-Pingstats introduced weighted pings for its relability calculation,
+Pingstats\cite{pingstats}, developed by cmeclax between 2000 and 2003 is a
+pinger written in C and shell scripts that are executed by the cron, a Unix daemon that executes programs at previously specified
+times. Pingstats introduced weighted pings for its relability calculation,
 giving older pings less weight than more recent data.
 
 % FIXME: if rlist didn't do the 'secret token in ping', mention it here
@@ -514,31 +547,29 @@
 to verify she got a correct set of mixes, without needing to know
 which parties are in the actual set of pingers.
 
+
 \begin{algorithm}
 {\bf Protocol UpdateMixes}
 
-% FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME
-% FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME FIXME
-% FIXME: revpar doesn't exist
-% \begin{revpar}
-%  \item r-broadcast new list ${\cal L}of mixes
-%  \item wait for $n-t$ r-broadcasts.
-%  \item {\bf receive} a set ${\cal L}'$ of mixes
-% \end{revpar}
-% \begin{revpar}
-%  \item run multivalued BA protocol, using  ${\cal L}'$ as an input
-%  \item {\bf receive} a set ${\cal L}''$ of n-t lists
-%  \item let ${\cal L}'''$ be the set of mixes that have been proposed by $t+1$ parties
-%  in the set.
-%  \item threshold-sign  (\em date, ${\cal L}'''$) using a threshold signature
-%scheme, getting the signature share$\sigma_i$
-% \end{revpar}
-%
-% \begin{revpar}
-%  \item r-broadcast the signature share $\sigma_i}
-%  \item wait for $n-t$ such shares
-%  \item combine the shares to retrieve $\sigma}
-% \end{revpar}
+\begin{revpar}
+ \item r-broadcast new list ${\cal L}of mixes
+ \item wait for $n-t$ r-broadcasts.
+ \item {\bf receive} a set ${\cal L}'$ of mixes
+\end{revpar}
+\begin{revpar}
+  \item run multivalued BA protocol, using  ${\cal L}'$ as an input
+  \item {\bf receive} a set ${\cal L}''$ of n-t lists
+  \item let ${\cal L}'''$ be the set of mixes that have been proposed by $t+1$ 
+  parties in the set.
+  \item threshold-sign  (\em date, ${\cal L}'''$) using a threshold signature
+   scheme, getting the signature share$\sigma_i$
+\end{revpar}
+
+\begin{revpar}
+ \item r-broadcast the signature share $\sigma_i}
+ \item wait for $n-t$ such shares
+ \item combine the shares to retrieve $\sigma}
+\end{revpar}
 \end{algorithm}
 
 \subsubsection{Update set of pingers.}
@@ -727,11 +758,11 @@
 
 \subsection*{Acknowledgments}
 
-The author of Echolot would like to thank Lucky Green and Colin Tuckley for
-writing end user documentation and keeping it current, Orange admin for work on
-the HTML templates that make up Echolot's output, and BiKiKii Admin, noisebox
-Admin and many nameless testes for providing valuable feedback during Echolot's
-development.
+The author of Echolot would like to thank Lucky Green and Colin Tuckley
+for writing end user documentation and keeping it current, Orange admin
+for work on the HTML templates that make up Echolot's output, and BiKiKii
+Admin, noisebox Admin and many nameless testers for providing valuable
+feedback during Echolot's development.
 
 
 \end{document}

***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxx with
unsubscribe freehaven-cvs       in the body. http://freehaven.net/