[freehaven-cvs] Add most of a conclusion section

[nickm@seul.org (Nick Mathewson)]

Update of /home/freehaven/cvsroot/doc/fc04
In directory moria.mit.edu:/tmp/cvs-serv22346

Modified Files:
	minion-systems.tex 
Log Message:
Add most of a conclusion section

Index: minion-systems.tex
===================================================================
RCS file: /home/freehaven/cvsroot/doc/fc04/minion-systems.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- minion-systems.tex	8 Sep 2003 21:18:24 -0000	1.1
+++ minion-systems.tex	8 Sep 2003 21:39:18 -0000	1.2
@@ -1,4 +1,4 @@
-
+% $Id$
 \documentclass{llncs}
 \usepackage{epsfig}
 \usepackage{graphicx}
@@ -85,8 +85,56 @@
 defeat traffic analysis.  We focus on Mixminion, an open-source
 application with a deployed research network.
 
+\subsection{Related work}
+
+\section{Mixminion: Open source strong anonymity}
+
+\section{Status and future work}
+The first public version of Mixminion was released in December of
+2002.  Since then, we have grown a deployed network of 22 testing
+servers,\footnote{As of 8 September 2003.} operated by volunteers in
+the US, Canada, and Europe.  The current codebase implements anonymous
+messages, anonymous replies, erasure-correcting fragmentation and
+reassembly, address blocking, reliable message delivery, and an
+automated server directory with key rotation.
+
+Before Mixminion is ready for broad-scale user adoption, however, more
+work remains, both in research and in implementation.  The largest
+areas ahead are, broadly:
+\begin{itemize}
+\item {\bf Usability and client implementation.}  For an anonymity
+  system to hide its users communications, it must have many users to
+  hide them among.  The current Mixminion client runs only from a
+  command line on Unix-like platforms, though a Windows32 client is
+  planned within the next few months.  For maximum user acceptance,
+  more work is needed to integrate Mixminion with existing email
+  applications.
+\item {\bf Distributed directory design.}  It's essential that all
+  users of the Type III network have an identical view of which
+  servers are available, reliable, and trustworthy.  The current
+  implementation uses a centralized directory, which gives the entire
+  network a single point of failure.  Our design calls for a more
+  distributed directory implementation.
+\item {\bf Pseudonymity.} Currently, there is no practical way to
+  maintain a long-term pseudonymous identity via Type III reply
+  blocks.  Although we have a specification for a workable pseudonym
+  server, the server is not yet implemented.
+\item {\bf Abuse prevention.} One of the best ways to attack users'
+  anonymity is by mounting a denial of service attack against some or
+  all of the Type III remailer network, in order to force users onto
+  compromised servers, or to force them to use insecure
+  channels. [XXXX say more.]
+\item {\bf Enterprise integration.}  The current implementation,
+  because of its volunteer roots, assumes that most installations are
+  for a single computer.  In an enterprise environment, however, it
+  could be more reasonable to integrate a single Mixminion as a part
+  of the outgoing email server.
+\end{itemize} 
 
+[XXXX Should we talk more about the academic/research side of our
+status?] 
 
+[XXXX have a real conclusion.]
 
 \bibliographystyle{plain}
 \bibliography{minion-systems}

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