- tor-dev - lists.torproject.org

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

27 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

How to run a headless second Firefox instance?
by David Fifield 26 Apr '14

26 Apr '14

We talked a while ago about using a browser extension to make HTTPS requests on behalf of a pluggable transport, so that the TLS doesn't stand out as unusual (#11183). I have that working pretty well and you can try it out. Using these bundles, you can run the meek pluggable transport and the TLS layer looks just like Firefox, because it is Firefox. https://trac.torproject.org/projects/tor/ticket/11183#comment:16 https://people.torproject.org/~dcf/pt-bundle/3.5.2.1-meek-5/ How it works: tor starts a wrapper program called meek-client-torbrowser, which starts a second copy of firefox using a separate profile.meek-http-helper. The second profile has some different prefs (https://gitweb.torproject.org/user/dcf/tor-browser-bundle.git/blob/861e270c…) and it runs the HTTP helper extension. The extension prevents a second browser window from opening. Once the second firefox starts up, meek-client-torbrowser runs meek-client and sets it up to communicate using the browser helper. What I need some advice on: In order to prevent a browser window from opening in the second instance of firefox, the helper extension opens a modal dialog and never returns. If the dialog is ever closed, the whole browser is shut down. It looks like this (https://gitweb.torproject.org/pluggable-transports/meek.git/blob/d2de8adc06…) try { // Block forever. var prompts = Components.classes["@mozilla.org/embedcomp/prompt-service;1"] .getService(Components.interfaces.nsIPromptService); prompts.confirm(null, "Query", "Get down, get funky?"); } finally { var app = Components.classes["@mozilla.org/toolkit/app-startup;1"] .getService(Components.interfaces.nsIAppStartup); app.quit(app.eForceQuit); } It gets the job done, but it sucks because the first thing you see is the dialog and you have to know not to close it. Is there a way to accomplish the same thing (keep the browser running, but don't show a browser window) without raising a conspicuous dialog? David Fifield

5 7

Tor Browser Weekly IRC meetings moved to 15:00 UTC Fridays
by Mike Perry 25 Apr '14

25 Apr '14

Due to the EU "Summer Time" changes generating new conflicts for a few people, the Tor Browser team's weekly IRC meeting will now be on Fridays at 15:00 UTC in #tor-dev on irc.oftc.net, starting this Friday, April 25th. For details on our meeting format, see the original post: https://lists.torproject.org/pipermail/tbb-dev/2014-February/000000.html -- Mike Perry

3 2

txtorcon v0.9.2
by meejah 25 Apr '14

25 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am happy to announce that txtorcon v0.9.2 is now available. This release adds a few minor bug-fixes and a few API enhancements. Full details: * add on_disconnect callback for TorControlProtocol (no more monkey-patching Protocol API) * add age() method to Circuit * add time_created property to Circuit * don't incorrectly listen for NEWDESC events in TorState * add .flags dict to track flags in Circuit, Stream * build_circuit() can now take hex IDs (as well as Router instances) * add unique_name property to Router (returns the hex id, unless Named then return name) * add location property to Router * TorState.close_circuit now takes either a Circuit ID or Circuit instance * TorState.close_stream now takes either a Stream ID or Stream instance * support both GeoIP API versions * more test-coverage * small patch from enriquefynn improving tor binary locating * strip OK lines in TorControlProtocol (https://github.com/meejah/txtorcon/issues/8) * use TERM not KILL when Tor launch times out (https://github.com/meejah/txtorcon/pull/68>) from hellais * Unit-test coverage now at 98% sha256 sums for the distribution files: 93e934f83e3fc6fcf40e76f7c9c28459af04205fb912d384aaacb7ac5269bb8f dist/txtorcon-0.9.2-py2-none-any.whl fe90743cdc453002ad046aa6556b611b4e85b813ff92865769d3d27712c2ca47 dist/txtorcon-0.9.2.tar.gz There are also signatures on github and txtorcon.readthedocs.org You may download from github or the hidden service: https://github.com/meejah/txtorcon/releases/tag/v0.9.2 https://github.com/meejah/txtorcon/releases/download/v0.9.2/txtorcon-0.9.2-… https://github.com/meejah/txtorcon/releases/download/v0.9.2/txtorcon-0.9.2-… https://github.com/meejah/txtorcon/releases/download/v0.9.2/txtorcon-0.9.2.… https://github.com/meejah/txtorcon/releases/download/v0.9.2/txtorcon-0.9.2.… http://timaq4ygg2iegci7.onion/txtorcon-0.9.2.tar.gz http://timaq4ygg2iegci7.onion/txtorcon-0.9.2.tar.gz.asc Source code: https://github.com/meejah/txtorcon/archive/v0.9.2.tar.gz Thanks, meejah -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJTWVf5AAoJEMJgKAMSgGmn07kIAKSwjBck76dyN1lWJj0fRl/f BevLpnp+rb+ge5hBAeKfsVTYciDBZeSo8/fE44wTNh5Qj9HEhFopVC4WF61rIFU+ 4IkpnFvfmVEd8Iu1vqQ/hFmP1jrvT8T+nTbaTGkcoCSPI+GyXkbxLqcl0Fncq51M M0OIRphyWA7EK3YoZ2Q1BOEIwsN0pwERYUhU0CGS45L7OZmyw86RXTMBZpBnNXrD 5VjQdpx8fvrV2iCRXi/k/e2Jy/xqs8o0I2+o9M6WrBiGCs5S9YbjsAKzRb7dsaBZ RlRAdKUjyzkquPl4K8E5ocDToB1hIGvqCSp7s11a5rq5T/jUiDMYrjkxIXH1Yg4= =W7+f -----END PGP SIGNATURE-----

1 0

Pluggable transports meeting tomorrow (Time changed!) (16:00 UTC Friday 24th of April 2014)
by George Kadianakis 24 Apr '14

24 Apr '14

Hello friends, just wanted to remind you that the regular biewekly pluggable transports meeting is going to occur tomorrow at 16:00 UTC. Place is the #tor-dev IRC channel in OFTC. Please note that we *changed* the time from 17:00 to 16:00 UTC. Thanks!

1 0

Q&A for meek pluggable transport tomorrow, 25 April, 18:30 UTC, #tor-dev
by David Fifield 24 Apr '14

24 Apr '14

Tomorrow, April 25, at 18:30 UTC / 11:30 PDT, in #tor-dev IRC, there will be a question-and-answer session on the meek pluggable transport. It will last about 45 minutes. Developers will be present to answer your questions. Background information: https://trac.torproject.org/projects/tor/wiki/doc/meek https://lists.torproject.org/pipermail/tor-dev/2014-April/006718.html https://lists.torproject.org/pipermail/tor-dev/2014-April/006719.html How to get on #tor-dev IRC: https://www.torproject.org/about/contact#irc David Fifield

1 0

Re: [tor-dev] [tor-talk] heartbleed: ETA for tor release(s) that blacklist affected directory authority keys? (#11464)
by anonym 23 Apr '14

23 Apr '14

21/04/14 12:27, Nusenu wrote: > Hi, > > the code to blacklist heartbleed affected tor directory authority keys > has been merged about a week ago [1]. > > Do you have an ETA on when you are going to release it (tor and TBB > packages)? As the release manager for the Tails 1.0 release I'm also interested in an ETA for this. Ideally the Tails image intended for the 1.0 release will be built on 2014-04-27 (so this is when we'll truly freeze the version of Tor), and released two days later. We Tails developers would find it sad if its core piece of software becomes out-dated immediately or even just shortly after that. Nick (or any one else in the loop), do you have any idea of timings for the next stable Tor release? Cheers!

2 3

GSoC : Rewrite Tor Weather
by Sreenatha Bhatlapenumarthi 23 Apr '14

23 Apr '14

Hi all, My name is Sreenatha(lucyd on OFTC). I am currently a final year undergraduate student at IIITH, majoring in computer science. I'll be rewriting weather this summer as a part of GSoC 2014. My mentors are meejah and karsten. In a nutshell, the weather rewrite project mostly involves two tasks, shifting the data backend to onionoo and closing the weather-specific tickets that are causing an issue at the moment. Besides these, there is also a plan to make use of a postgres database to store weather's subscription data. After this is accomplished, I'll document and test the new weather to make sure it's clean. Further details of my project proposal can be found at [1]. I'm very excited about working with Tor on this project and am happy to receive any sort of feedback and suggestions. Cheers, Sreenatha [1] - https://sites.google.com/site/sreenathadev/gsoc-2014-weather-rewrite

3 2

GSoC: BridgeDB Twitter Distributor
by Kostas Jakeliunas 22 Apr '14

22 Apr '14

Hi all, I'm excited to be able to spend another summer-of-code together with Tor (how impudent!) :) My name is Kostas (wfn on OFTC), primary mentor is isis and secondary mentor is sysrqb. I'll be working on writing a new BridgeDB Distributor[1]. I've set my primary task to designing and implementing a Twitter-distributor-bot (see proposal[2]): a Twitter bot answers personal (direct) messages, does rate control if needed, and gives bridge lines to users. There should be enough time to at least start on another distributor (right now I'm thinking about an XMPP-based one, as the federated-network-nature allows for some neat censorship circumvention approaches.) But there's also value in implementing a generic/core distributor that could give bridges to third-party distribution systems over a (say) RESTful API. Will see how things go, but core task for now is a twitter-based distributor. For further ideas, discussion, etc., see a separate tor-dev@ thread: https://lists.torproject.org/pipermail/tor-dev/2014-April/006742.html Ideas are very much welcome indeed! [1]: https://www.torproject.org/getinvolved/volunteer.html.en#newBridgedbDistrib… [2]: http://kostas.mkj.lt/gsoc2014/gsoc2014.html -- Kostas. 0x0e5dce45 @ pgp.mit.edu

1 0