diff options
author | Nick Mathewson <nickm@torproject.org> | 2005-01-22 01:35:29 +0000 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2005-01-22 01:35:29 +0000 |
commit | 1309885fcdf6c91ebc48ad84816212ef915173c2 (patch) | |
tree | 01f6deb4471d47e7e36e5585d0bf891a7b58b039 /doc/design-paper/challenges.tex | |
parent | fbb7f869c5cff8c771c73ab90f52d7017051693f (diff) | |
download | tor-1309885fcdf6c91ebc48ad84816212ef915173c2.tar tor-1309885fcdf6c91ebc48ad84816212ef915173c2.tar.gz |
Turn challenges.tex into minimally valid LaTeX
svn:r3411
Diffstat (limited to 'doc/design-paper/challenges.tex')
-rw-r--r-- | doc/design-paper/challenges.tex | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/doc/design-paper/challenges.tex b/doc/design-paper/challenges.tex index 62f9aee7c..dd310911a 100644 --- a/doc/design-paper/challenges.tex +++ b/doc/design-paper/challenges.tex @@ -1,8 +1,8 @@ +\documentclass[twocolumn]{article} +\title{Challenges in bringing low-latency stream anonymity to the masses (DRAFT)} - -Challenges in bringing low-latency stream anonymity to the masses - +\begin{document} \section{Introduction} @@ -27,7 +27,7 @@ useful network to a practical useful anonymous network. Tor works like this. -weasel's graph of # nodes and of bandwidth, ideally from week 0. +weasel's graph of \# nodes and of bandwidth, ideally from week 0. Tor has the following goals. @@ -100,7 +100,7 @@ continued money, and they periodically ask what they will do when it dries up. Logging. Making logs not revealing. A happy coincidence that verbose -logging is our #2 performance bottleneck. Is there a way to detect +logging is our \#2 performance bottleneck. Is there a way to detect modified servers, or to have them volunteer the information that they're logging verbosely? Would that actually solve any attacks? @@ -172,3 +172,5 @@ assuming that, how much anonymity can we get. we're not here to model or to simulate or to produce equations and formulae. but those have their roles too. +\end{document} + |