tor-dev March 2015

tor-dev@lists.torproject.org

76 participants
78 discussions

maintenance status of atlas or globe
by Nusenu 31 Mar '15

31 Mar '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, is globe or atlas actively maintained? Does it make sense to create trac entries? (I just want to avoid doing worthless things.) thanks, Nusenu -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVFqYBAAoJEFv7XvVCELh0u1QQAKSai+lYibASpYdqUFnfka7E APq5zGYnkR1I9KGTR8aL9+Z/dlEzl2fCCztwyfFZPYFudh/qzPtSPDUInLvDE/za 3X25hbCHwyW9Q7jQKAYWYuYWACE1S4F62e6TFzoT20gga1EhldBO+FqL943D7DuV 4FPT6lkWuPtZKF5X3gb0tkS6d48o5NYSp3RhFsowX2Y3SfdoRnTa86QbQ+2k9g7K R2W6f53c6jxwUU8MC4W3Tqc2JykojFbZADvwi8QxJ+4KlxWimG6PDshuJoY+sdsX R0n5o0L986uAn9CA5K5s/ANLkl9cYgt/oxptsY4HWSFKAh6xjdQBSYt5qjXI+KxL d1PDPdGXjolePsjUv/md+hnoRVjo4FCjx+5aQw23QhGaCi9Np0E87rF2xuUNmszs y9F/niXvNJMp1OIhVDeTinLm18lkOVCoGz/UkHdbiBj5md/5GTfql3zp2Nssku30 O+hUOEuvTJ0mousMglFeWRiO2UiliU55qTEbIUV5o4YVCK4uWA11v06so6dI4FNh bRwqUTsnzU/PqLdvgDUP3fiZXizVoxQB+KMzwnmroV+QmL+cnAR7ac8hU/PfPH/F nC/lONV5ZiXnmBZXvHTnIUBeHRwtQi48rDWtNLnSQmRN3i8jwP1NiUmuyKXZgA2a 6+cGVMKBA+Xy2sBciw9y =2YsQ -----END PGP SIGNATURE-----

5 9

#14997: canonical path to tor alpha debian repo
by Nusenu 30 Mar '15

30 Mar '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Erinn, it would be great if there was a canonical path to tor alpha releases (like the RPM repo provides) so people that choose to use alpha releases would not have to change their apt sources.list as soon as a new major tor version is released. What do you think about #14997? https://trac.torproject.org/projects/tor/ticket/14997 I guess this would not be big effort - simply creating a subfolder for the alpha builds would do it? thanks, Nusenu -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVGTW8AAoJEFv7XvVCELh0zmIP/2Whg3TTSFVXTmvV4dz0oJaq 5caVsMJcKqeNXSxhg5hs4oVVpJco5wSdMrFkz384svFNGvhbnEsPxVy24tLjUw0O EUUzw6MQ4nbL4sEV9AjjVDKTcvPPM9l4jTfLb5/l49j6X9TNmW/DLJ3qm3/KHlM/ ny3Jzm9fXIu37WjkBfGJf5FDspLNKSOVkLj2tSXe/DURZ86caRH+HJkWD6cu4A+L QtfgZgFrmSS1oLwXsvt8PB5b7Hf7uoQlNoAJiS1WneEYlREZA1B9Jj/hdjtbUbaE pS46bFGghl6l8JVkaheHauCkc5sCXQegRQ4b4280ENmGqNcWyVQiIHwJ0q1xiI5G 88oMniG3SAELvsTBWd9idH2gkvst82qtHpq8kpA0Vk1TvbL1M6gI9YECf7f2VeMi w2zZSCgeCmI509GEsG53PiR2uj+7VGPSbSTeUlLXBOx9u0Qlt8UHhSwR58LJrp7C 79RzJxoXbJKWhPmNjIbcr2xX4TYyIqtmPvq6NCq3DpF73X/XrNPE9hF2t1PHPbR5 3rhgt4NyU65Oj8T79CHn1u7Lgd2VGaYf3hVnAHd+M1R270APhGu30Qur+Y6ta/54 3m0Ai81QRdxXZSJbRGZiAUhEh+bq1MMrj/aFZtBaVzT0tT5pDcdnIzAKeLPSbsRT UkiJp34p8BB6FoFel1uc =Znzj -----END PGP SIGNATURE-----

1 1

What is the unit of the bw reported in the descriptor?
by Thee Chanyaswad 30 Mar '15

30 Mar '15

Dear all, Following the earlier question about the gap between total bw reported, what is the unit of the bw shown? The Torspec doc says it's in Byte/s. Is this still correct? Thank you very much. Best Regards, Thee

2 1

HS bi-weekly community meeting
by Isabela 29 Mar '15

29 Mar '15

Hello there, I am very sorry for this to be taking so long. I keep forgetting about it! I created a poll for us to pick a day/time and start a bi-weekly meeting for the HS community. This was something we spoke in Valencia and the members of the community think is a good idea (a place to talk about HS in general not only sponsorR stuff). The times proposed at the poll are the most common time we meet (in UTC time) and for the slots where there is no meeting going on at #dev-tor. http://doodle.com/xnxugpt9fb7rvch2 Please vote! Thanks isabela

2 3

Renaming arm
by Damian Johnson 29 Mar '15

29 Mar '15

Hmmm, thread about something as squishing and infinitely debatable as a name. What could go wrong? But before you get excited I've already picked one, this is just to sanity check with the community that I'm not making a stupid mistake... again. Five years ago when I started arm [1] I had the following criteria for picking its name... 1. It needs to be short. This is a terminal command so anything lengthy is just begging people to alias it down. 2. It should be reasonably memorable. Sorry, no 'z62*'. 3. No naming conflict with other technical things. Body parts though are fair game though. Clearly the name failed at #3. When I picked it the ARM processor was just barely becoming a thing, but time marched on and now every irc discussion goes... new_person: New relay operator here, any tips? somebody: Hey, try arm! new_person: The processor? I'm so confused now. somebody: Nope, something completely different. It's a confusing name. I'm rewriting the whole bloody codebase so why not fix this along the way? So without further ado the name I've picked is 'Seth'. It's easy to type (#1), memorable (#2), and from what I can tell no SETH processors are on the horizon. I've reserved the name on PyPI, and searchs on wikipedia looks fine (most interesting match is the Egyptian god [2], which is actually kinda neat). So now just a final sanity check with you, our wonderful community. Any strong reasons to pick something else? Nothing is set in stone yet so still open to alternatives. Cheers! -Damian [1] https://www.atagar.com/arm/ [2] https://en.wikipedia.org/wiki/Set_%28mythology%29

13 23

Damian's Status Report - March 2015
by Damian Johnson 29 Mar '15

29 Mar '15

Guten tag world! Time again for another status report... -------------------------------------------------------------------------------- Arm Graph Panel Rewrite -------------------------------------------------------------------------------- Really? Has it actually been four months? Dusted off my work from November and finished rewriting arm's graph panel. Besides untangling a mess of code that would make my family disown me, this leverages 'GETINFO bw-event-cache' to greatly improve graph prepopulation. Thanks, Nick, for adding that! Coding aside, real challenge this month has been finding a better name. Thanks everyone who has helped (especially Mike!)... https://lists.torproject.org/pipermail/tor-dev/2015-March/008398.html I'm now strongly leaning toward Nyx. Brevity aside, Nyx is the primordial goddess of the night with a description that's positively delightful... "Her appearances are sparse in surviving mythology, but reveal her as a figure of such exceptional power and beauty, that she is feared by Zeus himself. She is found in the shadows of the world and only ever seen in glimpses." Very curious to hear what the community thinks. -------------------------------------------------------------------------------- New Development Blog -------------------------------------------------------------------------------- Five years now I've dumped my status reports onto a single page. While this worked, clearly it lacked a certain... elegance. Moved to a proper blog... * before: https://www.atagar.com/log.php * after: http://blog.atagar.com/ Personally I found it interesting how my style has evolved over the years. My current approach is to focus on a couple topics, followed by a brief list of additional things I've been up to. This is much easier to skim than the walls of text I once wrote. -------------------------------------------------------------------------------- Few other noteworthy things were... * Stem can now read encrypted hidden service introduction-points. (#15004) * Support for the consensus' new packages field and new HS extrainfo stats. * You can now specify just a single test to run, rather than a whole module. (#14944) * clv expanded our tests to check if tor has capabilities Stem lacks. (#8250) * Sebastian sped up our integ tests by making them use trigger-able events. (#14943) Cheers! -Damian

1 0

Tor Browser 4.5a5 will change circuit expiry to 2hrs
by Mike Perry 28 Mar '15

28 Mar '15

In Tor Browser 4.5a5, we decided to increase MaxCircuitDirtiness to 2 hours (https://trac.torproject.org/projects/tor/ticket/13766). Because we also use Tor's SOCKS username isolation using the URL bar domain as the SOCKS username in Tor Browser 4.5 now, this has the effect that websites you visit will continue to use the same circuit (and thus the same exit IP) for all of their content elements for 2 hours, or until you click "New Identity" or "New Tor Circuit for this Site" (which appeared in Tor Browser 4.5a4). The reasons for this change are detailed in that ticket description, but in summary I think it is a really, really bad user experience when a website switches languages, bans you, or logs you out every 10 minutes. My own workflow in Tor Browser has been frequently interrupted by this in ways that have caused lost work and/or lost access due to this problem. With this change in combination with the "New Tor Circuit for this Site" Torbutton menu option, you now have the ability to get a good circuit for a site that you can actually use long enough to get something done. However, there are some downsides to this change: 1. Longer circuit lifetimes may mean more memory consumption at relays. 2. Longer circuit lifetimes may make correlation easier for adversaries that run Tor nodes or can see inside TLS (by stealing node keys). 3. Longer circuit lifetimes may distinguish Tor Browser users at the Guard node. 4. Longer circuit lifetimes may mean that the Tor client is less able to adapt to transient changes in Tor relay overload - the load conditions that caused the Circuit Build Timeout code to pick your current path may have long since changed over the span of 2 hours. 5. We actually had to hack update, OCSP, and favicon requests to continue to use 10 minute circuits, because Firefox does not make it easy to determine the URL bar associated with them. (We opted to keep the circuits for these requests at 10 minutes to avoid excessive linkability at the exit.) Did I miss any? Long term, I think what I'd rather do to achieve this functionality is to create a "TrackIsolationExits" Tor feature that ensures that Tor Browser keeps the same exit IP for a given URL bar domain independent of the underlying circuit lifespan, as I mentioned in https://trac.torproject.org/projects/tor/ticket/15458#comment:2. So: How do we make the decision as to if it is more important to improve usability in the short term while we design and implement "TrackIsolationExits", or if the above concerns (and others) trump poor usability? Right now, I am inclined to make the choice that leads to more people being able to effectively use Tor Browser in the short term, and then try to provide a better solution that gives similar user-facing behaviors with better network usage properties in the long term. To complicate matters, as ticket #15458 indicates, there are several other security concerns related to circuit use by Tor Browser that also need to be ironed out. In particular, it is actually somewhat dangerous to allow websites to use a new circuit every 10 minutes for things like Javascript/AJAX requests, because this enables Guard discovery. SOCKS isolation and a long circuit lifespan may actually make such Guard discovery harder, but unfortunately, there may still be other ways to do this in Tor today (See https://trac.torproject.org/projects/tor/ticket/13669 and https://trac.torproject.org/projects/tor/ticket/7870). Thoughts? -- Mike Perry

5 8

Measurement of the amount of discrimination by website operators on Tor users?
by Rishab Nithyanand 28 Mar '15

28 Mar '15

Hey all, I was wondering if anyone could help me figure out the status of this blog post (from August 2014): https://blog.torproject.org/blog/call-arms-helping-internet-services-accept… Specifically this part: "Step one is to enumerate the set of websites and other Internet services that handle Tor connections differently from normal connections, and look for patterns that help us identify the common (centralized) services that impact many sites". I think it's an important step to help make more informed decisions about how the usability of Tor can be improved (by reducing discrimination). I've got a measurement platform in place, some ideas of how I'd like the study to be done, and an awesome mentor to help me with it. But I'd like to know if it's already been accomplished by someone else before investing time into it. Thanks! Rishab

2 1

onionoo-announces
by Nusenu 28 Mar '15

28 Mar '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Karsten, the latest onionoo update 2.3 triggered a bug in my onionoo "client" (charset encoding). Even though it is a bug on my side, would you mind announcing future releases/deployments on onionoo-announce [1] including a short changelog? thanks, Nusenu [1] https://lists.torproject.org/pipermail/onionoo-announce/2015/thread.html -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVFeWsAAoJEFv7XvVCELh0aeYP/R9pkcPgMGttspr5cl1W1RM+ qeIutnhNDAMs+DcbHKmB19BzgSRUfzrm4DCqnizWIxdXcF+AQP2nhmP0y+hIWTrK 5ctBQsWMUiwHym0TcKbbIEHrP2BcIoQSIM1GG52G4OWfmoymjbi5J1Jd+KuXYsFr 8GtJlLkjHWcD8wQuCUtMSfq1tTK/XnQES/UfhTUfJ3TMZvR1wxD3BNWZFJSOFMP2 k7cfBLYSG2uRCyRZ8dkoLXnSeJ/aya2PqR41mvU5y+IdUHC8IoVItx3GhC4ZT2v1 YcQyxvVFZh0NEwrdnYIxErNN5CJjqDUyLPWVQPJGvKR1KgFVdtcqsJH8OsyvYW1y ysETJ9AXPReo9os+oAWVJZvFG1HwU6MzS4U7beuVMo3drzNh3433nkZbCX50hS4z WMUdsWjZgUNscAIj76ECI58wiTgYN8Ro5X9wY9LwSwJz7NHtc+a999xSLy3GUuUp vEerRa1k06PqeqpNsZoe/8WVwohZVtRc9oGTcXJgtRF3F3hltsqB6s03hGLsQfXJ roOFglxrUlBaGAVYlyLWHSDiPf2lVnNUF27nsGodjoTLEubsJ1BsxUqT1JTNi3yx k8WTU2ATfbTVKva0N7Ac3yBE8+ZkQ+YbZB839li9ocXuxi173/aNmG3mKOVWWhP2 x0C/WXllxI2ObZY05ryR =IfVc -----END PGP SIGNATURE-----

2 1

Localization
by Abhiram Chintangal 26 Mar '15

26 Mar '15

Hi, I ran into a user, who was asking for censorship circumvention tools that have been translated to indic languages ( Bengali, Hindi, Tamil and Telugu to name a few). Is there a separate mailing list for localization efforts? I would appreciate it if someone can point me to the right resources. Cheers! -- Abhiram Chintangal

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-dev March 2015