- tor-dev - lists.torproject.org

Revising Proposal 140
by Daniel Martí 01 May '14

01 May '14

Hello everyone, Last week I introduced myself [0] on this list, shortly after being accepted into GSoC to work on Consensus Diffs. My GSoC proposal is heavily based on the Tor proposal #140 [1], which is close to being six years old now. This is why, after some discussion with Nick, Sebastian and Weasel (the original author of the proposal), it became obvious that it needs some revising. Here are the improvements we discussed on IRC: * Microdescriptors didn't exist back then, so the proposal makes no mention of microdescriptor consensus diffs. We should support these too. * Weasel added the 's' command just so that a line with just one dot could be produced. Since consensuses should never have such a line, I think it would be best to drop 's' and not support such a line as an input when generating the diffs. * In response to my introduction mail, Ian mentioned that fetching a diff is leaking data about when you last used Tor. Nick proposed to have a time limit on these diffs, to e.g. 24 or 36 hours, which should mitigate this problem. * Regarding their size, #140 suggests that they are not useful past 16 hours. I thought we could compare the compressed size of the diffs when creating them, since they may be of use for a longer time. We could do this relative size limit first as well as the time limit mentioned above. That is all that we came up with for now, what do you think? Ideas about what might be missing or needing an update are welcome, of course :) Regards. [0] https://lists.torproject.org/pipermail/tor-dev/2014-April/006744.html [1] https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/pro… -- Daniel Martí - mvdan(a)mvdan.cc - http://mvdan.cc/ PGP: A9DA 13CD F7A1 4ACD D3DE E530 F4CA FFDB 4348 041C

3 5

Damian's Status Report - April 2014
by Damian Johnson 01 May '14

01 May '14

Hi all. This April's status report is gonna be short and sweet. The bulk of my time went toward Google Summer of Code student selection. I'm delighted to announce that we have thirteen great students working with us this summer (twelve with Tor and one with the EFF)! This is twice as many as last year, so it will be interesting to see if we can manage it. https://trac.torproject.org/projects/tor/wiki/doc/gsoc This concludes the bulk of my work as the org admin, so this next month I should be able to focus back on writing sweet, sweet code. On April 26th I presented at LinuxFest Northwest. For those who haven't seen it, this was a repeat of my TA3M 'Tor Ecosystem' presentation... http://linuxfestnorthwest.org/2014/sessions/tor-ecosystem-developers-guide-… https://media.torproject.org/video/2013-11-t3am-damian-johnson.mp4 And last but not least, bit by bit I've been picking away at a feature branch for Stem. It's not quite ready yet, but expect an announement and a new Stem release sometime in May. One improvement that *is* now available though is the following: The connection module's connect_port() and connect_socket_file() functions have been deprecated in favor of a new, slicker connect(). https://stem.torproject.org/api/connection.html#stem.connection.connect This new function is quite a bit smarter about the error responses it provides, and is more intuitive to use. Cheers! -Damian

1 0

Tor Specs
by Ahmed 01 May '14

01 May '14

Hello Everyone, Is this the latest version of Tor specification protocol? https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=tor-spec.t… -- Ahmed <ahmed(a)linuxism.com>

2 1

New events calendar
by Ximin Luo 30 Apr '14

30 Apr '14

Hi all, I decided to create a new calendar, since the old one is out-of-date and we seem to have lost the access. View as a web page: https://www.google.com/calendar/embed?src=dt92shou5q1ooe1kptubhclo4s%40grou… Import into your calendar program: https://www.google.com/calendar/ical/dt92shou5q1ooe1kptubhclo4s%40group.cal… If anyone would like write-access, or for me to make a one-off change, just ask! Please also update any links to the old calendar in trac; I forget where they all are. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git

1 0

TOR compilation with MinGW
by primster primster 30 Apr '14

30 Apr '14

Hi, i’d like to compile tor in my mingw installation, how could i achieve the same results as you: https://www.torproject.org/dist/win32/ It will be awesome to have tiny client as soon as possible in one exe Could you please give me full instruction or shell script ? -- Regards!

1 0

GsoC: Revamp GetTor
by Israel Leiva 28 Apr '14

28 Apr '14

Hi all! My name is Israel Leiva, and I'll be working on the "Revamp GetTor" [1] project during this GsoC. My mentors will be sukhe and mrphs. What I propose is to redesign the current "GetTor" code in order to make it oriented to modules, which the users can access via common "services" (like SMTP, for instance) and get the required info (packages or links). The idea is that this new design could allow the implementation of new modules in the future. You can find more details about my proposal in [2]. Needless to say I'm very excited and honored to collaborate with the Tor project and community! [1] https://www.torproject.org/getinvolved/volunteer.html.en#revamp_gettor [2] http://ileiva.github.io/gettor_proposal.html Best, -- israel

2 2

Version bump of obfsproxy to 0.2.8 in TB breaks FTE
by Kevin P Dyer 28 Apr '14

28 Apr '14

Hi Mike, It looks like [1] broke FTE [2]. Can you hold off on pushing any releases public, until we resolve #11629? George - Can we revert obfsproxy back to 0.2.4, to give me time to sort this out? -Kevin [1] https://gitweb.torproject.org/builders/tor-browser-bundle.git/commit/ce30cd… [2] https://trac.torproject.org/projects/tor/ticket/11629

2 2

GetTor Meeting (April 29)
by Sukhbir Singh 27 Apr '14

27 Apr '14

Hi, We will be having our first meeting on revamping GetTor in #tor-dev tomorrow from 20:00 - 20:45 UTC. Israel Leiva is the GSoC student who will be working on improving GetTor over the summer so we are looking for suggestions from the community on how we can improve the bundle distribution. (Sorry for the short notice and duration but everyone's schedule seems to be busy!) -- Sukhbir

1 1

GSoC: Pluggable Transports Combiner
by quinn jarrell 26 Apr '14

26 Apr '14

Hi everyone, My name is Quinn Jarrell and I'm a student University of Illinois at Urbana Champaign. I'm excited to join GSoC and I'll be working on building a pluggable transporter this summer for Google summer of code. The pluggable transports combiner will allow transports to be chained together to form more varieties of transports and make them harder to detect and block. You can read more about it here: [0]. My mentors are Infinity0 and dcf. My IRC name RushingWookie, and you'll often see me lurking in #tor-dev. I'm excited to work for Tor this summer and I can't wait to get started. Quinn Jarrell [0] https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Combi…

2 1

Please help testing a new Onionoo version that uses Gson to format documents
by Karsten Loesing 26 Apr '14

26 Apr '14

Hi everyone, [I'm blind-copying everyone who I know has been working on an Onionoo client in the past. If you received two copies of this email, or if you received this email even though you're not subscribed to tor-dev@, and you don't want to be informed of updates related to Onionoo, please let me know.] Please help testing the Onionoo version running here: http://54.81.197.70:8080/onionoo/ This version uses Google's Gson library to format JSON documents, rather than concatenating strings that happen to represent JSON documents (#11577). While this change doesn't sound very difficult, it required quite a few code changes. This is good, because the new code is much cleaner. I'm just not certain whether I broke things. Please try to point your Onionoo client to the new Onionoo version and see if something breaks. Please also try edge cases and give this Onionoo instance a hard time. Just note that this version only contains a few days of data. Things to try out in particular: - Responses contain less whitespace than before. Please make sure that your client handles the more compact responses correctly. - UTF-8 characters in details documents should still be in escaped form, e.g., \u00F2 for the ò in Filastò in the contact field. Other fields that might contain UTF-8 characters are city_name, as_name, etc. - The fields parameter for details documents required some hacking, so I might have broken it. I'm planning to deploy the new version on yatei in 5--7 days from now. If you find a bug, please either comment on #11577 or open a new ticket, whatever seems more appropriate. Thanks for your help! All the best, Karsten

2 2