- tor-dev - lists.torproject.org

traversing the source code of tor
by H S 10 Jun '13

10 Jun '13

Hi there, We would like to implement some specific protocol in Tor as an implementation project. Our one of pseudo codes that we have to take into account is the one mentioned on the paper under the link http://www.cypherpunks.ca/~iang/pubs/UC-OR.pdf , page 5, figure 2. I would like to know how can I connect or relate this pseudo code with the Tor source code to help us understand where we should insert our desired modification on the source code of the Tor. For instance in the first of the pseudo code line we have "upon an input (setup):". And know in which file/lines of the Tor source code we have this?

2 1

Re: [tor-dev] stem
by Damian Johnson 10 Jun '13

10 Jun '13

> Hi, Damian, thanks. I am happy to discuss it on tor-dev@. But I want to keep > off spam, which some of my questions at first may be, essentially Qs. But, > if you think they would be of interest to tor-dev, or others could help, > just let me know, and i will sign up for it. They certainly are! If you're interested in tor and development then I would definitely suggest being on that list. Including it for this thread. > I am trying to figure out how to pull in the nodes that are actually used in > my Tor circuits. They are the nodes reflected in the Network map function. You want the get_circuits() method. As you mentioned the 'path' attribute has the relays in your present circuits... https://stem.torproject.org/api/control.html#stem.control.Controller.get_ci… > I have created a MySql DB of some of my Tor circuits and nodes which i am > analyzing. I grabbed 48 circuits with their 144 nodes and info (IP address, > nickname, country) manually from my laptop's Tor network map. That certainly sounds painful. The circuit paths will provide the relay fingerprints which you can use for get_network_status() to get the address, nickname, ORPort, etc... https://stem.torproject.org/api/control.html#stem.control.Controller.get_ne… As for locales that would be done via get_info('ip-to-country/<address>')... https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt#l672 > ... and ultimately to AS and country. AS will require the Maxmind AS database or something else. I know that Onionoo includes the AS information so the options that come to mind are either to (a) see how it does it or (b) query Onionoo for this information. https://onionoo.torproject.org/ > And i have read much of the control-spec, don't know how much is out of date The control-spec should be up to date. If there are any inaccuracies then please let us know! Did you have any other questions? -Damian On Mon, Jun 10, 2013 at 4:44 AM, SARAH CORTES <sarah(a)lewis.is> wrote: > Hi, Damian, thanks. I am happy to discuss it on tor-dev@. But I want to keep > off spam, which some of my questions at first may be, essentially Qs. But, > if you think they would be of interest to tor-dev, or others could help, > just let me know, and i will sign up for it. > > For example, I am trying to figure out how to pull in the nodes that are > actually used in my Tor circuits. They are the nodes reflected in the > Network map function. I have read your fine stem tutorials, it is so > impressive you have dome so much work and documentation on your own > initiative. It is certainly a huge help to me and otter researchers like me. > > I have created a MySql DB of some of my Tor circuits and nodes which i am > analyzing. I grabbed 48 circuits with their 144 nodes and info (IP address, > nickname, country) manually from my laptop's Tor network map. I am analyzing > their country, so I am seeking to map nickname or fingerprint of the node to > IP address and ultimately to AS and country. Ultimately, I am analyzing > jurisdictional arbitrage and the hostility factors of differ countries to > Tor traffic, and whether it is possible to incorporate country or AS in to > the Tor path algorithm. > > I can see the entry guard nicknames and fingerprints in my state file and > pick them up there, if necessary. Wish i could just edit the logs to display > all nodes, then figure out how to map the node fingerprint or nickname to > its IP address them AS and country. I understand there is a Tor atlas > function but have not read it carefully yet. > > I have read documentation on the contents of the consensus file, the > descriptors, geoip and state files, and played around with them a bit to > understand them. I grasp that a fingerprint is a hash of the node's public > key, and one or both of which seem to be the most reliable ID for a node. > > I can see from your documentation that variable path(nickname, fingerprint) > contains the data i want. Just need to be able to get that data easily. Not > sure if editing my torrc file is the way or what. If you have any > suggestions, they are much appreciated. > > And i have read much of the control-spec, don't know how much is out of date > https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt > > I have read this on modifying torrc, and played around with modifying torrc, > on an elementary basis: > https://www.torproject.org/docs/faq.html.en#torrc > > and some tickets on modifying torrc > https://trac.torproject.org/projects/tor/ticket/6147 > > and what I believe is your excellent documentation on stem events; > https://stem.torproject.org/api/response.html#stem.response.events.Bandwidt… > > > > > > > > On Jun 8, 2013, at 2:31 PM, Damian Johnson <atagar(a)torproject.org> wrote: > > Hi Sarah. Yup, I'd be more than happy to help if you have any stem > questions. Email would definitely be better since we look to keep > missing each other on irc. I'd appreciate it though if we discussed it > on the tor-dev@ email list... > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > > On Sat, Jun 8, 2013 at 3:42 AM, SARAH CORTES <sarah(a)lewis.is> wrote: > > Hi Damian, I'm Sarah Cortes, a researcher. I tried you on irc on #tor-dev > but was unable to reach you. We met at the tor dev meeting which i attended > in March. I have some Qs for you regarding stem. Please let me know if you > are available, thanks > >

2 1

Gitian-based Deterministic Build System for TBB (Need MacOS Help!)
by Mike Perry 10 Jun '13

10 Jun '13

Over the past couple weeks I've been redoing the TBB build system to use Gitian to produce alpha TBBs using Tor Launcher instead of Vidalia. I have succeeded in producing deterministic, localized builds of TBB for Linux and Windows. This means that independent people all over the world can now easily produce their own bundles for these platforms fresh from sources, and have their bundles exactly match the bundles the Tor Project releases, down to the SHA256 hash. If we leverage this property wisely, it will allow us to defend against targeted attacks against our bundlers and their build machines, and even ultimately ensure the integrity of our bundles in the event of key compromise of the gpg keys used to sign the bundles. My plan for this is for there to be between 2-3 official signers for each bundle, where each person produces their build independently, and signs the (identical) result files. To further protect against targeted attack, in addition to these 2-3 official signers, we need some people to be "secret verifiers". Ideally these people would not be publicly affiliated with the Tor Project, but would still produce their own bundles anyway. If their SHA256 ever fails to match the signed bundles, that person should anonymously open a trac ticket (using the cypherpunks account) and attach the bundle files that differ for analysis. The differing files can be found easily enough with 'diff -r'. To ensure the existence of these "secret verifiers", I believe that the official signers should occasionally conspire to conduct "Fire Drills", where they all agree to alter the bundle in some innocuous way (such as adding whitespace to a config file or a Firefox JS file), and ensure that a verifiers anonymously report the verification failure. In future versions of Tor, we should probably add a consensus field consisting of a url to a file that lists the current recommended bundle hashes and versions, along with the current SHA256 of that file, to anchor the bundle authentication the Tor's current trust root (the 9 dirauth keys). To try out the new build system, please see the README, and let me know where the system could use clarification or improvement to make it easier to use: https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gi… The build system has some quirks that are worth mentioning: 1. It requires you run it from either an Ubuntu 12.04 or above host with KVM support, *or* you run it from an Ubuntu 12.04 or above chroot/VM. The bundle scripts try to detect your current situation and suggest that you "export USE_LXC=1" from your shell if you need to, to cause the system to use LXC instead of KVM (so that you can build from an Ubuntu VM or on a machine that does not otherwise support KVM). 2. We currently have no MacOS support. To support MacOS, we need to create cross-compilers for it so that we can produce builds from the Gitian VMs (which again are Ubuntu). A few people have done this. I have sent them mail asking for instructions on how to reproduce their compiler packages: http://www.tarnyko.net/en/?q=node/9 https://launchpad.net/~flosoft/+archive/cross-apple/+packages http://wiki.freepascal.org/Cross_compiling_OSX_on_Linux Unfortunately, at least one of those URLs say that to produce a cross-compiler, you need access to an OSX SDK. Since I do not have a Mac that is currently supported by recent OSX SDKs, and since we *really* want to be sure that the cross-compilers we produce use code from a fresh known-good SDK install, I won't be doing this. Please let me know if you'd like to help tackle this problem. In the meantime, I am going to work on the rest of the "Short Term" TODO items, and produce official alpha bundles for Linux and Windows, so we can test Tor Launcher in an official alpha release. Here's the TODO file: https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gi… Happy building! -- Mike Perry

3 6

Academic Project Guidance
by mahesh 09 Jun '13

09 Jun '13

Hi, I am final year undergraduate student at Pune Institute Of Computer Technology, Pune, India. I have to do a academic project in span of 6-months with other three students.I am looking for a mentor who would discuss ideas with us and provide proper guidance. Also I am also interested under working an organization's guidance. Please interested people let me know. Sincerely, Mahesh

1 0

Format-Transforming Encryption Pluggable Transport
by Kevin P Dyer 09 Jun '13

09 Jun '13

Last September I announced initial results [1] towards a framework, which we call Format-Transforming Encryption (FTE), for encoding messages using regular languages. We're excited to announce that we've made progress towards an implementation and would like to invite alpha testers. Our source code is available on github [2]. Tor Bundles are available for OSX/Linux [3] that include our FTE framework and are configured by default to work with FTE+Tor bridges deployed in the United States. Unfortunately we don't, yet, support Windows. The latest version of our paper is available on the Cryptology ePrint Archive [4]. In the paper we describe our framework and provide a comprehensive security evaluation of FTE's success in evading six DPI systems --- including using regular expressions from open-source DPI systems to evade detection by a closed-source black-box commercial DPI system. By "evade" we mean that it's easy for FTE to tunnel arbitrary TCP streams (e.g., Tor) such that they are (mis)classified by DPI systems as a configurable target protocol (e.g., HTTP, SMB, RTSP, etc.) of one's choosing. We release FTE in its alpha stage because we believe it is well positioned to evade the suspected protocol white-listing [5] recently reported in Iran. More generally, we're optimistic FTE has long-term potential as a tool to enable users to control how their traffic is classified by passive DPI systems. As one example, over the last month, we've successfully tunneled Tor through the Great Firewall of China, using FTE to make our traffic "look like" HTTP. We're eager for feedback on this alpha release, so please do not hesitate to contact us with questions. -Kevin P Dyer (and his co-authors) [1] https://lists.torproject.org/pipermail/tor-dev/2012-September/003993.html [2] https://github.com/redjack/FTE [3] https://github.com/redjack/FTE/tree/master/TorBundles [4] http://eprint.iacr.org/2012/494 [5] https://lists.torproject.org/pipermail/tor-dev/2013-May/004787.html

1 0

Pluggable transport bundles with websocket transport
by David Fifield 09 Jun '13

09 Jun '13

I have made new experimental pluggable transports bundles with support for the websocket transport. We hope this transport looks enough like HTTP to get past certain firewall filters. https://people.torproject.org/~dcf/pt-bundle/2.4.12-alpha-2-websocket1/ If the transport name websocket sounds familiar, that's because it's the same transport used by flash proxy. The difference here is that you connect directly to the bridge, rather than going through a browser proxy. The actual software is the websocket-client program from here: https://gitweb.torproject.org/flashproxy.git/tree/HEAD:/websocket-transport Due to a build SNAFU, the OS X packages have the flashproxy transport disabled, with only obfs2, obfs3, and direct websocket enabled. The other platforms have all transports enabled. We would like to have some more fast websocket relays to include in the default torrc in a future release. If you can do this, see the section "How to run a relay" from https://gitweb.torproject.org/flashproxy.git/blob/93be0302:/README#l100 Send the IP address and port of your relay to tor-assistants(a)lists.torproject.org. David Fifield

1 0

Ideas for metrics of the safety of the Tor network
by George Kadianakis 08 Jun '13

08 Jun '13

A year ago or so, during FOCI '12, with the help of some smart people [0] I compiled a list of interesting metrics/visualizations that could help us understand the security of the Tor network. Since even more people are interested in metrics lately, I thought of posting this list here, in case it inspires someone (better than letting it rot unseen). Note that some of the stuff in the list might have been implemented already, and there are also some upcoming academic papers that explore this area. Also, check out https://trac.torproject.org/projects/tor/ticket/6460 In any case, I'm inlining the list: """ 1 Attacker strategy 1.1 Are there certain geographic or network locations where adding relays with a given capacity will most influence your safety metrics? This influence could be positive ("where should I put my relay to best help the Tor network?") or negative ("where should I put my relay to best attack users?"). 1.2 What happens to the network if X relays are compromised? 1.2.1 All Windows relays. 1.2.2 All relays running old Tor versions. 1.2.3 All "top 10% relays" are compromised... 1.3 How much bandwidth do I need to compromise, in order to compromise a random user's path in a given timeframe 1.3.1 Use 'guessing entropy'? 1.4 Is there a difference between compromising a '5Mbit relay' and 'five 1Mbit relays'? Should there be a difference? 1.5 Change classic Tor formula to start considering bandwidth load balancing. 1.5.1 "If an adversary controls m out of n nodes, he can correlate at most (m/n)^2 of the traffic." should consider bandwidth 1.6 See how many exits are exiting on a different IP than the one they accept traffic? (they can sniff twice) 2 Network diversity 2.1 How many relays are running old Tor versions? 2.2 Fraction of paths that have the entry and exit at the same country/AS. 2.3 Fraction of paths that pass twice through AMS-IX/LINX/DE-CIX. 2.4 What happens to the network if we discard relays of certain characteristics? 2.4.1 What happens if we discard the slowest relays? 2.4.2 What happens if we cap the fastest relays? 2.4.3 Discard paths with expected high latency (http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf) 2.5 If only a given fraction of exit relays support IPv6, how much does it reduce your anonymity to be going to an IPv6-only destination? 2.5.1 Should we add a fourth hop, like we do in exit enclaving? 2.6 Is there any relationship between the rate of new relay arrival (e.g. during political events or after popular conferences) and the level of diversity of these relays? 2.7 Graph showing "the X% of the relays see Y% of the traffic" 2.7.1 example, "The 5% of the relays route 55% of the traffic"... 2.7.2 Lorenz Curve / Gini coefficient (Used in "Improving Security and Performance in the Tor Network through Tunable Path Selection") 2.8 Measure router families and how much bandwidth they control/how many circuits they can compromise. 2.9 What is the security difference if families did not exist? 2.10 How much does the /16 subnet restriction influence path selection? 3 Optimization results 3.1 Robustness over time: is an adversary that can knock out X% of the capacity in the network (for various values of X) getting more or less influential as the network grows? How about an adversary who can knock out an absolute capacity of K bytes for various values of K? 3.1.1 Look at the vailability/uptime/whatever of relays and YOU decide which relay has the guard flag. 3.1.2 Is weighted uptime the correct way of assigning a guard flag? Relay with 4 days of uptime gets flag, relay with one day down and three weeks of uptime does not get the guard flag. 3.2 If we give out Guard flags according to some other algorithm, how much safety can we get back? 3.2.1 Safety measures 3.2.2 Alternative guard algorithms 3.3 In Tor 0.2.1.x we started load balancing based on active bandwidth measurements, so we use the bandwidth weights in the network consensus rather than the weights in each relay descriptor. We know that change improved performance, but at what cost to safety? 3.4 What happens to the network diversity if we put a low cap on the bandwidth weighting of any node that hasn't been assigned a measurement by the bandwidth authorities yet, to protect against relays that lie about their bandwidth? If there's no real effect, we should do it; but if there's a large effect, we should find a better plan. 3.5 What if some Tor users choose their paths to optimize a different network property (like latency or jitter), as suggested by Micah Sherr? The infrastructure you've built to measure diversity here should apply there too. 4 Notes 4.1 Modularize the path selection code of pytorctl for researchers to use. 5 Papers to read 5.1 Trust-based Anonymous Communication: Adversary Models and Routing Algorithms 5.2 Latest version of Tariq's "Changing of Guards" paper 5.2.1 Look at "Closed Analysis" section in appendix 5.3 Improving Security and Performance in the Tor Network through Tunable Path Selection 5.4 Metrics for Security and Performance in Low-Latency Anonymity Networks (PDF) (Cached: PDF) """ [0]: the list includes Aaron Johnson, Ian Goldberg, Tariq Elahi, Roger, Nikita Borisov, and more that I can't remember right now.

1 0

Reduce RTT for preemptively built circuits (GSoC)
by ra 08 Jun '13

08 Jun '13

Hello everyone! During this year's Google Summer of Code I[0] will be working on reducing the Round-Trip-Time (RTT) for preemptively built circuits.[1] My mentors are Mike and Aaron. A brief summary of the project: RTTs of circuits can be measured by violating the exit policy of the exit node and the resulting error can be timed in a measuring client. It is assumed that the RTTs are Fréchet-distributed which could be used to reject a preemptively built circuit if its RTT is below a certain threshold value. A basic algorithm will be implemented to gather the required data for further statistical analysis which should help answering open questions like: • Are the RTTs Fréchet-distributed? • Does this strategy make new attacks feasible? • How many probes per circuit are needed to do reasonable estimations? • How much additional load is added to the network? • What is an appropriate cut-off percentile? • Does the strategy work in terms of anonymity and performance? • Does the RTT vary for destination ports? (This might be the case for destination ports that occur rarely in exit policies.) • Does this strategy also work if guard nodes are congested? Best, Robert [0] "ra_" on OFTC [1] http://www.google-melange.com/gsoc/project/google/gsoc2013/ra_/19001

2 1

Censorship Simulator Virtual Machine GSoC
by Arturo Filastò 08 Jun '13

08 Jun '13

Hi Johannes, I wanted to introduce you and your GSoC project to the list. The project is about building a virtual machine based censorship simulator. The goal is to have a way to test if the ooniprobe tests are working properly by simulating the network of a censor. Our goal is to actually run the software that a censor would be running (e.x. squid, bluecoat proxy sg va, etc.) and detect it's presence in an as real as possible environment. Johannes and Klaudiu analyzed a bit of the possible technological solutions to making this here: https://trac.torproject.org/projects/tor/wiki/doc/OONI/CensorshipSimulator. I think that the outcome is that we will be using Vagrant, meaning that this simulator could then be run on OSX, Linux and Windows. The kind of networks we will be creating are those where: * There is a transparent HTTP proxy * There is NAT * Certain sites are blocked thanks to HTTP headers * RST packets are sent when connecting to certain hosts * DNS based censorship is present If you have some ideas of things you would like to see in this, add ideas to this ticket: https://trac.torproject.org/projects/tor/ticket/7233, or create a page in the trac wiki nested under https://trac.torproject.org/projects/tor/wiki/doc/OONI/CensorshipSimulator. ~ Art.

2 1

Creating a p2p identity authentication protocol
by DataPacRat 07 Jun '13

07 Jun '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As suggested by Tor Project's helpdesk, I'm forwarding this message to tor-dev, in hopes that I might be able to evoke any useful references, suggestions or commentary. - ---------- Forwarded message ---------- From: Matt Pagan via RT <help(a)rt.torproject.org> Date: Fri, Jun 7, 2013 at 4:42 PM Subject: [rt.torproject.org #10568] Adapting 'tag' URI into p2p identity authentication system To: datapacrat(a)datapacrat.com You should subscribe to the tor-dev mailing list and bring this up on that public mailing list: https://lists.torproject.org On Fri Jun 07 18:02:44 2013, datapacrat(a)datapacrat.com wrote: > I'm working on the initial stages of a project which seems likely to > be of use to many who use the Tor protocol; and which could itself > likely benefit from the experience of the people who build and use Tor > extensively. > > I am currently looking into creating a new URI based on 'tag:' ( > http://www.taguri.org/ , https://tools.ietf.org/html/rfc4151 ) to use > for distributed reputation systems. I would like a common protocol so > that this idea can be easily expressed: "Authority A says that X and Y > are the same person" (with an optional field for the certainty of that > statement) (with an optional comment field) (with an optional > authentication hash). It seems likely to be simple to implement the > new URI (perhaps called 'nym:') in existing mail/contact software, so > that nym: links can be automatically imported into contact lists to > update them. > > Might you be interested in helping me work this out; or pointing me in > the direction of anyone else who might be? > > > Here's an initial draft of what I mean: > > > nym:Authority[,DateTime]:(Identity1)[,date];(Identity2)[,date][;(Identity3)[,date]][?comment1[&comment2][#authenticationHash] > > While based on 'tag:', there are a number of changes from that URI's > format: > > The authority can be not only an email address or a domain name, but > some other identifier, such as the URL of a social media profile, such > as http://twitter.com/DataPacRat or http://www.facebook.com/DataPacRat > . > > The date is no longer limited just to a particular date, but can be > specified (using ISO 8601 format) down to a particular second, for any > rapidly-changing identities. > > The identities can be plaintext names, social media profile URLs, > library card numbers, or any other chosen identifiers; though > regularly-formed URIs, email addresses, and domain names are most > likely to be most common. > > The comment fields are left incompletely defined, to allow for future > expansion; such as to indiciate trustcloud whuffie scores, how the > authority knows the individual being identified, or anything else that > someone comes up with. It seems a good idea to suggest the use of > existing fields from vCard and FOAF, to ease interoperability. > > By default, if a comment field is a number, that number is assumed to > be how confident the authority is that all the listed identifiers all > refer to the same individual, measured in decibans. (Decibans are > logarithmic, with 0 decibans being equivalent to 1:1 odds, or being > 50% confident; 10 decibans to 10:1 odds, or ~90% confident; 20 > decibans to 100:1 odds, or ~99% confident; and so on.) It is > recommended that these numbers be integers, unless there is a specific > reason to be able to specify confidence to greater accuracy; and with > a magnitude under 128, as it requires extraordinary effort to have 100 > decibans of confidence for even the most fundamental facts. > > (This method also implicitly allows for revocation of an identity > referral, simply by using a negative number instead of a positive > one.) > > The authentication hash is to provide strong evidence that the listed > authority is actually the one making the assertion. By default, it is > assumed to be based on whatever public cryptographic key (eg, > PGP/GnuPG or X.509) is linked to the listed authority ID; and that > what is being signed is the string of text before the hashmark. > > > This could allow for something like the following: > > nym:datapacrat@datapacrat.com:(datapacrat@datapacrat.com),2013-06- > 05;(http://twitter.com/DataPacRat),2013-06-05;(Daniel > Eliot Boese)?100&TrustCloud,774&Klout,29#randomhashofletters > > ... to indicate that as of that particular date, I indicate with > maximum confidence that my name, email address, and Twitter account > all point to me, and that I have two social media scores. (I would > have used 127 decibans instead of 100 if I'd just been asserting my > own identity.) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32) iQEcBAEBAgAGBQJRskfVAAoJEBrKNlQrJtDDHWoIAKn6wCfrQhinNC6zCvf2D3eS CuSKB0XFPkm903ZwzA29aZKnhC6MJGO78Pu5pUuwZg0oWfB6zJshvmQR9A+QQdif s0Y84iNoeqVHqAqZgCk3sXPxqaNyEU2yEWREr09qNqVmuu6vhxODNInXf46PjV/6 BAlb26Ea75UwZfMpKY7rxYprTkIbkx3/55r16v8bZyKCKEkcb+0QQWf/pXA114eD Ec9YXIBEdPDrrhDOe2hAhJWI3ul3pcf/BK13Ch2ngSp757jxGJrz5QxmGNIu+bgQ Us1SPBS/e8JI9xX2xOa3p/CAh/McxfzFWqPO78t2v77bn/sl45WLfl4RoQ7ulvc= =9XrL -----END PGP SIGNATURE----- Thank you for your time, -- DataPacRat "Then again, I could be wrong."

1 0