March 2014 - tor-dev - lists.torproject.org

Fwd: About using source code
by saurav dahal 22 Mar '14

22 Mar '14

Can anybody please tell me how to use the original source code of tor by modifying and implementing on the TOR network? For example: I want to log how many circuits have been made through my OR. Thanks, Saurav

3 5

Tor integration into CACHeCoin
by kalgecin 22 Mar '14

22 Mar '14

Hey guys, I'm looking into integrating TOR network into CACHeCoin. The idea is, by default, the coin should connect through the tor network, with the option of disabling it and connecting normally. This will help boost some anonymity within the coin and help the TOR network by keeping up the nodes :-) The idea is, if the person activated connection through tor (which is already by default) he'll be able to receive stake. If he disables, No stake will be generated. Unfortunately i don't have much free time to dig into the tor code, but will be happy to receive the pull request on github https://github.com/kalgecin/CACHeCoin/ Please let me know what you think -- Kalgecin http://code.google.com/p/kalgecin *https://github.com/kalgecin <https://github.com/kalgecin>* https://plus.google.com/u/0/104834274682757290524<https://plus.google.com/u/0/104834274682757290524/posts> https://twitter.com/kalgecin

3 3

Panopticlick summer project
by Gunes Acar 21 Mar '14

21 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear All, My name is Gunes Acar, a 2nd year PhD student at Computer Security and Industrial Cryptography (COSIC) group of University of Leuven. I work with Prof. Claudia Diaz and study online tracking and browser fingerprinting. I'd like to work on "Panopticlick" (https://www.torproject.org/getinvolved/volunteer.html.en#panopticlick) summer project and other fingerprinting related issues which I tried to outline below: 1) Collaborate with Peter@EFF to port/open-source Panopticlick: https://trac.torproject.org/projects/tor/ticket/6119#comment:4 a) implement necessary modifications - e.g. we won't be having cookies or real IP addresses to match returning visitors. b) consider security implications of storing fingerprints (e.g. what happens if someone gets access to fingerprint database?) 2) Add machine-readability support outlined in Tor Automation proposals: https://people.torproject.org/~boklm/automation/tor-automation-proposals.ht… a) which one(s) should we implement? JSON, YAML, XML? 3) Survey the literature for fingerprinting attacks published since Panopticlick. Implement those that may apply to TBB: a) Canvas & WebGL fingerprinting (Mowery et al.) - make sure the patch at #6253 works b) JS engine fingerprinting (Mulazzani et al.) c) CSS & rendering engine fingerprinting, (Unger et al.) ... 4) Check with realworld fingerprinting scripts to see if they collect anything that is not considered before. Check if TBB's FP countermeasures work against them. (We can use data from FPDetective study to find sites with fingerprinting scripts) 5) Backport new "attacks" found in 3 & 4 to EFF's Panopticlick in case they consider an update. 6) Convert fixed FP-related bugs into regression tests. https://trac.torproject.org/projects/tor/query?keywords=~tbb-fingerprinting… 7) Build test cases to check the severity of fingerprinting related open tickets, e.g.: https://trac.torproject.org/projects/tor/ticket/8770 https://trac.torproject.org/projects/tor/ticket/10299 8) Work on potential fingerprinting bugs that ESR31 may bring. 9) ESR transitions seem to create a lot of FP-related issues that need to be checked manually (e.g. #9608). Consider developing a tool that iterates over the host objects of two browsers to compare them automatically (e.g. to pinpoint new objects, new methods, updated default values, etc.). Similar to "diff tool" mentioned here: https://people.torproject.org/~boklm/automation/tor-automation-proposals.ht… 10) Evaluate the font-limits of TBB by checking the average # of fonts Top 1 Million sites use. We can either collect fresh data with FPDetective or use the existing (~1 year old) data. More on my background relevant to fingerprinting and TBB code base: We recently published a paper called "FPDetective: Dusting the Web for Fingerprinters" (CCS'13) to measure the prevalence of browser fingerprinting on the Internet. As a part of this study, we built instrumented browsers from Chromium and PhantomJS source code and developed a framework to detect fingerprinting (https://github.com/fpdetective/) I also got my hands dirty with the TBB source code to seek vulnerabilities in FP countermeasures. Two ways I found to circumvent existing font limits were as follows: https://trac.torproject.org/projects/tor/ticket/8270#comment:2 https://trac.torproject.org/projects/tor/ticket/5798#comment:13 Other pointers: My website: http://www.esat.kuleuven.be/cosic/?page_id=126 FPDetective website: https://www.cosic.esat.kuleuven.be/fpdetective/ My (first & only) Tor patch: https://trac.torproject.org/projects/tor/ticket/10472 My Tor FAQ profile: http://tor.stackexchange.com/users/731/gacar Looking for your comments, Cheers, Gunes N.B.: I won't be applying to GSoC. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTJmUiAAoJEPb7JcMmVt4g4jAH/2JLUKPGo52JpfsHeMtLZgQm JVoEELKuNVjwJ5KqgO4OhIqpS6yl/cggLsUe19fNrC5I++5w5lGWM3JRqCU/T5OV PLwRrs1lc1wU2zWkcKN/uvZyFys1xAsA2NzyYRZdKOjoGiDI8a3wgYM/o8a5PSt0 +wTJ6OdtRpFuXk9CrxUScx6kbLEYCoQeGcAmQe+ZIUWo6CzeQr/3yP8Jz7B3Uyqq ccSJACFuif2naQFiCDqyuQLIZu/9jMFGbYMg81OhZeeOWhmq4FwCjZOR8bzj8zqV i3N8hFXTRSYLjOg5AWVX+JMsCWJAX3rTrYe6X5GKA/tIm1gMJhwtedfaE38eHOM= =2stA -----END PGP SIGNATURE-----

3 6

Descriptor-id and responsible hidden service directorate. Changes in version 0.2.4.18-rc - 2013-11-16
by Frank Young 21 Mar '14

21 Mar '14

I have noticed that since the release of version 0.2.4.18-rc - 2013-11-16, Attempts to fetch v2 rendezvous service descriptor are failing. The issue seems to get worse as many people are updating their clients. The calculation of decriptor ids based on specification in rend-spec.tx <descriptor-id = H(permanent-id | H(time-period | descriptor-cookie | replica))> doeesn't seems to be correct anymore. All 6 responsible hidden services directorates return 404 to a GET request for /tor/rendezvous2/<base32_encode[descriptor-id]> I search through the tor source for the release version (0.2.4.18-rc - 2013-11-16) in rend_compute_v2_desc_id and rend_client_refetch_v2_renddesc but failed to notice any significant change. Could any member of the dev team respond to to this?

2 3

GSOC- Revamp GetTor
by Kiran Mathew Koshy 21 Mar '14

21 Mar '14

Hi everyone, My name is Kiran Mathew Koshy and I'm a student of IIT Patna, India. I''m interested in participating in Google Summer of Code 2014 under Tor project. GetTor is a service that I had tried a couple of months ago when tor was blocked by our sysadmin, and I believe revamping getTor will have huge impact on avoiding censorship. *TL;DR version*: 1. A system by which a user has multiple routes of obtaining the tor browser- dropbox , mega, google drive, and a couple of other file sharing sites 2. If the user provides their pgp key, an encrypted reply can be sent 3. If the user requests so, the file sent should be password-protected , plus some random data(in a single file) should be added along with the tor browser in order to have variable file sizes. 4. Some file sharing sites(most) allow you to transfer a file between accounts. This is a bit unnecessary, but can be implemented if there is time left. 5. NLP: A very simple natural language processor to process the email and to scavenge for the requested configuration- language, os, file sharing site, etc. Example mail: "please send me a tor browser bundle ( English) that works on Windows. Could you send it through Mega ?" . 6. An email proxy- To counter the small chance that the mail server doesn't allow emails to gettor(a)gettor.torproject.org. Chances of this are low in my opinion, since gmail/ any other mail service is usually available. *Details and explanation*: 1. In most cases, a sysadmin or an ISP can block known bridges, torproject sites, and tor nodes. In this case, *the only way to ensure that a user can access the tor browser software is by allowing multiple sources to download it from. * The practice of blocking File sharing sites is also common, so sites like dropbox, google drive, box, etc are also important. The code will be written in a modular format such that addinga new file sharing site would be equal to adding a couple of urls of their REST API, or at most, writing a new module consisting of 10-15 lines of code. I have worked with the APIs of file sharing sites before, and most are quite similar. 2. If PGP keys are sent, an encrypted reply follows. No brainer. 3. Bundling the software with a file of random size into a password protected tar would prevent snooping based on size of the https request. A little bit far fetched, yes, but good if you are up against your government. This would prove to be cpu intensive and network intensive, since the server will have to encrypt the file and upload it to a file sharing site every time someone requests it. Therefore, this will be limited to one or two instances at any given time. It is also possible to upload multiple instances of encrypted tor browser software, and store the keys in the server. 4. Self Explanatory 5. An NLP would be very simple to implement in this case, in order to fish out the keywords and choose the correct configuration. Example mail: "please send me a tor browser bundle ( English) that works on Windows. Could you send it through Mega ?" . The keywords in this case would be: 1. tor browser bundle. 2. English. 3.Windows 4.Mega. A list of such keywords will be stored on the server. I believe an NLP would be better than the current arrangement. 6. Self Explanatory. Since the current getTor doesn't come close to this, I believe it is best to *rewrite it, reusing select parts*. I havce a good experience in C++ and Python. I completed Google Summer of Code 2013 under Wikimedia Foundation, so this is my second year for GSOC. Since I'm a bit late to apply, I will be submitting this as a proposal right away. Please comment on any changes you would like to incorporate in this. -- Kiran Mathew Koshy Electrical Engineering, IIT Patna, Patna, India

1 0

Tor Browser Weekly IRC meetings moved to 18:00 UTC Fridays
by Mike Perry 20 Mar '14

20 Mar '14

Due to the US Daylight Savings Time changes generating new conflicts for a few people, the Tor Browser team's weekly IRC meeting will now be on Fridays at 18:00 UTC in #tor-dev on irc.oftc.net, starting this Friday, March 21st. We will be snuggling up next to the Huggable^W Pluggable Transports team meeting, which is just before us at 17:00 UTC on alternating Fridays. Their next meeting is March 28th. The hope is that this will help us to work closer with them to polish up the new unified PT-enabled Tor Browser, add new transport types, and otherwise generate PLUR (yeah, I said it). For details on our meeting format, see the original post: https://lists.torproject.org/pipermail/tbb-dev/2014-February/000000.html P.S. We may have to revisit this time again when the EU switches to "Summer Time" on March 30th. Running an hour later in the EU may start to run into people's Friday evening plans, but we'll cross that bridge once it starts burning. -- Mike Perry

1 0

GoSC - Website Fingerprinting project
by Marc Juarez 20 Mar '14

20 Mar '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lunar: > Have you read Mike Perry's long blog post on the topic? > https://blog.torproject.org/blog/critique-website-traffic-fingerprinting-at… > > It outlines future research work in evaluating the efficiency of > fingerprinting attacks, and also mention a couple of promising defenses. Yes, I am aware of it and I'm currently working on a study to evaluate the efficiency of these attacks. As Mike Perry said in the post, most of the attacks give an unrealistic advantage to the adversary and probably countermeasures work much better than what has been shown so far. However, some of the results of these articles suggest that there exist coarse-grained traffic features that are invariant to randomized pipelines (RP, SPDY) and thus can still identify web pages (Dyer et. al.). Also, edit-distance based classifiers broke some old versions of the RP implemented in Tor Browser. It's an open problem to see if these features actually uniquely identify web pages in larger worlds than the ones considered in the literature. In any case, link-padding strategies are specially designed to conceal these features with the minimal amount of cover traffic and are becoming affordable in terms of bandwidth. The project I propose would be directed to address this bug ticket: https://trac.torproject.org/projects/tor/ticket/7028 For example, I would like to implement the common building blocks for link-padding countermeasures (such as a "traffic generator controller" in the onion proxy and the entry guard). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTHz3kAAoJEGfJ5xfgazlxOwoH/ilP01mjxyyeuPbko/xkKGfw 5gMJGFa0m4StabJ1bhbqJWF2jsu6W2SBCVCqea0emvOvab0WzhuvQvzQb2obZpzr NReUhhiGRhj4xN+2yAL3Vh8zoyZigKtSQPoykwa/AFG7TvIGppHZb0S5ii7Hk/Yf UtwO3Kt3YCGJT3FoKEJQgN2wz82Skbo4Xiw0bknemPFmIkxlxyplkkD0D34OdEYx YPPxRBMuEnpa1H5H3bPMXK55kBP91qS5fg23hsN6Gksy45yhLeiOJZBi0n3nlHD2 xtp4sWdQhTUDFP85kSmbzW/eufuc4WAI6k5KeZtc5YrmIl9eOnAu+tG8Ghu4Vpc= =Rf6n -----END PGP SIGNATURE-----

4 7

Re: [tor-dev] Torbirdy
by mujnabed＠gmail.com 19 Mar '14

19 Mar '14

Hi, I've submitted my project proposal on Improving Torbirdy for review on Google Melange as suggested. If you guys can verify the proposal and suggest any modifications that would be great. My Name is Debanjum in case I haven't mentioned earlier. Thanks D

2 1

Interested in GSoC - Hidden Service Naming or Hidden Service Searching
by Jeremy Rand 19 Mar '14

19 Mar '14

Hi Tor developers, I'm interested in participating in GSoC. I'm an undergrad majoring in computer science at University of Oklahoma, and I've been a major Tor enthusiast for years. There are two possible projects which I'm considering; I'm looking for some feedback on which you think would be better for me to apply for. One project is allowing hidden services to have human-readable names. I think Namecoin would be an excellent backend for this. I coded a proof-of-concept of using Namecoin to point human-readable .bit domains to .onion domains; that code is available at https://github.com/JeremyRand/Convergence . For example, using this, you can visit http://federalistpapers.bit/ to get to the Federalist Papers hidden service. The proof of concept only works on Firefox right now (not TorBrowser); I would definitely be interested in porting it to TorBrowser, improving its privacy, and making it work for applications other than web browsing. Namecoin also has the useful feature of allowing HTTPS fingerprints to be embedded in the blockchain, which eliminates the need to trust certificate authorities for clearnet HTTPS websites (I understand that malicious exit nodes messing with TLS is currently a significantly voiced concern for Tor). I have a strong understanding of how Namecoin's DNS works and have developed some projects using Namecoin (including a dynamic DNS client), so I think I'm a good fit for such a project if there's interest in the Tor community. I talked with Jacob Appelbaum about using Namecoin recently; he was concerned about a 51% attack. I think that could be mostly resolved via a checkpointing system; while doing so adds a small degree of centralization, Tor is already slightly centralized, and it's still less centralized than other alternative naming systems that have been proposed (e.g. having Tor Project maintain a list of names themselves). While I'm not particularly familiar (yet) with how checkpointing is done within Namecoin's block validation system, I do know how to at least verify whether the currently loaded blockchain matches a given checkpoint (which would at least alert users that an attack had taken place). The other project is making a search engine for hidden services (listed as Project Idea F on the Tor website). I think YaCy could be used to accomplish this in a decentralized and censorship-free way. I would suggest making a separate YaCy network for hidden services, using a regexp whitelist to only index .onion URL's (YaCy has such a network but I think it's currently inactive). YaCy doesn't have whitelist support built in, but I think the blacklist feature should be usable for simulating such a feature with some effort. YaCy's SOLR schema supports searching based on outgoing link URL's, so I think I could make a standard YaCy client search for all clearnet sites which link to a .onion/.onion.to/.tor2web.org URL, and feed those URL's to a Tor YaCy client for indexing. I've been a YaCy enthusiast for a couple years, and I'm actually using YaCy in a grad-level CS project this semester (the course is on Artificial Neural Networks and Evolution), so while I haven't touched the YaCy source code, I think I'm a good match for this project. Do either of these sound like good proposals? Is one significantly more likely to be approved than the other, so that I know which to submit? Thanks, -Jeremy Rand

3 7

Re: [tor-dev] Panopticlick summer project
by Yan Zhu 18 Mar '14

18 Mar '14

(resending to tor-dev because the original message didn't go through) On 03/16/2014 11:52 PM, Yan Zhu wrote: > On 03/16/2014 07:59 PM, Gunes Acar wrote: >> Dear All, >> >> My name is Gunes Acar, a 2nd year PhD student at Computer Security and >> Industrial Cryptography (COSIC) group of University of Leuven. >> >> I work with Prof. Claudia Diaz and study online tracking and browser >> fingerprinting. I'd like to work on "Panopticlick" >> (https://www.torproject.org/getinvolved/volunteer.html.en#panopticlick) >> summer >> project and other fingerprinting related issues which I tried to >> outline below: > > Hi Gunes, > > I think all of these projects below would primarily be with EFF, not Tor > directly. Peter and/or I would be your point of contact; I'm not > familiar enough with Panopticlick at this time to give you much feedback > on the ideas below, so I cc'ed Peter. > >> >> 1) Collaborate with Peter@EFF to port/open-source Panopticlick: >> https://trac.torproject.org/projects/tor/ticket/6119#comment:4 >> a) implement necessary modifications - e.g. we won't be having cookies >> or real IP addresses to match returning visitors. >> b) consider security implications of storing fingerprints (e.g. what >> happens if someone gets access to fingerprint database?) > > Peter, what's the blocker on this? It sounds like Tor folks really want > it to happen soon, so I'm happy to take the lead on helping get this > open-sourced from the EFF side. > >> >> 2) Add machine-readability support outlined in Tor Automation >> proposals: >> https://people.torproject.org/~boklm/automation/tor-automation-proposals.ht… >> a) which one(s) should we implement? JSON, YAML, XML? > > No input here. > >> >> 3) Survey the literature for fingerprinting attacks published since >> Panopticlick. Implement those that may apply to TBB: >> a) Canvas & WebGL fingerprinting (Mowery et al.) - make sure the patch >> at #6253 works >> b) JS engine fingerprinting (Mulazzani et al.) >> c) CSS & rendering engine fingerprinting, (Unger et al.) > > This sounds greatly useful. Another good place to look is Mozilla's bug > tracker (https://bugzilla.mozilla.org/) > >> 4) Check with realworld fingerprinting scripts to see if they collect >> anything that is not considered before. Check if TBB's FP >> countermeasures work against them. (We can use data from FPDetective >> study to find sites with fingerprinting scripts) > > Same as above. > >> 5) Backport new "attacks" found in 3 & 4 to EFF's Panopticlick in case >> they consider an update. > > Yes, I'm happy to get those updates into EFF's instance. > >> 6) Convert fixed FP-related bugs into regression tests. >> https://trac.torproject.org/projects/tor/query?keywords=~tbb-fingerprinting… >> >> 7) Build test cases to check the severity of fingerprinting related >> open tickets, e.g.: >> https://trac.torproject.org/projects/tor/ticket/8770 >> https://trac.torproject.org/projects/tor/ticket/10299 >> >> 8) Work on potential fingerprinting bugs that ESR31 may bring. >> >> 9) ESR transitions seem to create a lot of FP-related issues that need >> to be checked manually (e.g. #9608). Consider developing a tool that >> iterates over the host objects of two browsers to compare them >> automatically (e.g. to pinpoint new objects, new methods, updated >> default values, etc.). Similar to "diff tool" mentioned here: >> https://people.torproject.org/~boklm/automation/tor-automation-proposals.ht… >> >> 10) Evaluate the font-limits of TBB by checking the average # of fonts >> Top 1 Million sites use. We can either collect fresh data with >> FPDetective or use the existing (~1 year old) data. > > All of the above sounds fine. > > Assuming that we can get Panopticlick open-sourced, I'm more than happy > to help you with any of these subprojects. > > -Yan > (EFF Staff Technologist / HTTPS Everywhere maintainer) >

3 3