Challenges in deploying low-latency anonymity (DRAFT) Roger Dingledine1, Nick Mathewson1, and Paul Syverson2 1 The Free Haven Project <{arma,nickm}@freehaven.net> 2 Naval Research Laboratory <
[email protected]> Abstract. There are many unexpected or unexpectedly difficult obstacles to deploying anonymous communications. Drawing on our experiences deploying Tor (the second-generation onion routing network), we describe social challenges and technical issues that must be faced in building, deploying, and sustaining a scalable, distributed, low-latency anonymity network. 1 Introduction Anonymous communication is full of surprises. This paper discusses some unexpected challenges arising from our experiences deploying Tor, a low-latency general-purpose anonymous communi- cation system. We will discuss some of the difficulties we have experienced and how we have met them (or how we plan to meet them, if we know). We also discuss some less troublesome open problems that we must nevertheless eventually address. Tor is an overlay network for anonymizing TCP streams over the Internet [13]. It addresses limitations in earlier Onion Routing designs [17, 27, 35, 36] by adding perfect forward secrecy, con- gestion control, directory servers, data integrity, configurable exit policies, and location-hidden services using rendezvous points. Tor works on the real-world Internet, requires no special priv- ileges or kernel modifications, requires little synchronization or coordination between nodes, and provides a reasonable trade-off between anonymity, usability, and efficiency. We deployed the public Tor network in October 2003; since then it has grown to over a hun- dred volunteer-operated nodes and as much as 80 megabits of average traffic per second.