- tor-project - lists.torproject.org

Infographic about Pluggable Transports
by Nima Fatemi 11 Jun '16

11 Jun '16

Attention: Metrics, UX and PT teams =================================== I'm working on an infographic about Pluggable Transport, that is ideally going to help educating both end-users and bridge operators (including potential bridge operators). I've prepared a list of things we could cover on this. Please review and let me know if there's anything I've missed that should be added to the list. This infographic is going to have two sections, the first part is more of a how-to. Showing 6-8 steps, demonstrating how to download Tor Browser and configuring it to use a PT to connect to Tor network. The second part, is the actual infographic part: - List of PTs included in Tor Browser with a one-line summary and significance of each - List of PTs under development - Stats + Total number of PT bridges + Average number of PT clients per day + Maybe compare the numbers with direct connections? - Links to PT page (on website and wiki) What are other interesting numbers about PT world? Is there anything else I should add to this? I was thinking about adding average traffic the default bridges are getting per mounth, since it's very significant. 'Azadi' alone has transferred more than 103 TBytes since Feb: month rx | tx | total | avg. rate ------------------------+-------------+-------------+--------------- Feb '16 12.07 TiB | 13.48 TiB | 25.56 TiB | 87.62 Mbit/s Mar '16 16.81 TiB | 18.84 TiB | 35.64 TiB | 114.31 Mbit/s Apr '16 11.17 TiB | 12.59 TiB | 23.76 TiB | 78.74 Mbit/s May '16 7.16 TiB | 8.07 TiB | 15.23 TiB | 48.84 Mbit/s Jun '16 1.55 TiB | 1.73 TiB | 3.28 TiB | 57.62 Mbit/s Best, -- Nima 0XC009DB191C92A77B | @mrphs "I disapprove of what you say, but I will defend to the death your right to say it" --Evelyn Beatrice Hall

4 4

Fwd: Mozilla Will Fund Code Audits For Open Source Software
by Damian Johnson 10 Jun '16

10 Jun '16

Considering how closely we work with Mozilla I suspect this program is no surprise, but none the less forwarding it along since it could very well benefit some of our sub-projects. Cheers! -Damian ---------- Forwarded message ---------- From: Slashdot: manishs <atagar2(a)gmail.com> Date: Fri, Jun 10, 2016 at 7:45 AM Subject: Mozilla Will Fund Code Audits For Open Source Software To: atagar1(a)gmail.com Reader Orome1 writes: The Mozilla Foundation has set up the Secure Open Source (SOS) Fund, whose aim is to help open source software projects get rid their code of vulnerabilities. Projects that want Mozilla's help must be open source/free software and must be actively maintained, but they have a much better probability to being chosen if their software is commonly used and is vital to the continued functioning of the Internet or the Web. Three open source projects -- PCRE, libjpeg-turbo, and phpMyAdmin -- have already gone through the process, and the result was removal of 43 vulnerabilities (including one critical). [![](https://a.fsdn.com/sd/twitter_icon_large.png)](http://twitter.com/home?status=Mozilla+Will+Fund+Code+Audits+For+Open+Source+Software%3A+http%3A%2F%2Fbit.ly%2F25PgTSg) [![](https://a.fsdn.com/sd/facebook_icon_large.png)](http://www.facebook.com/sharer.php?u=https%3A%2F%2Fnews.slashdot.org%2Fstory%2F16%2F06%2F10%2F1418216%2Fmozilla-will-fund-code-audits-for-open-source-software%3Futm_source%3Dslashdot%26utm_medium%3Dfacebook) [![Share on Google+](http://www.gstatic.com/images/icons/gplus-16.png)](http://plus.goo… [Read more of this story](https://news.slashdot.org/story/16/06/10/1418216/mozilla-will-fund-c… at Slashdot. ![](http://feeds.feedburner.com/~r/Slashdot/slashdot/~4/VLQ1G2rQYWM) URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/VLQ1G2rQYWM/mozilla-will-fu…

1 0

[machine usage] crm, ubuntu1404lts-persona
by Peter Palfrader 07 Jun '16

07 Jun '16

Hello gentle people! I am looking over the machines that tor is paying for, and two of them are the 1984 machine that we have labelled only as crm and ubuntu1404lts-persona. I think they may have been created at one point by Andrew. Does anybody know who might be using these machines? If you have an idea, please let us know. If one of them is your machine, or at one point was, please let us know if it is still useful and we should keep it around. (And please briefly describe what it is being used for.) If I don't hear anything, and nobody objects either, I will stop having them auto-renewed, i.e., I will decommission them. Thanks. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `- https://www.debian.org/

2 3

Notes from June 2 2016 Vegas team meeting
by Karsten Loesing 07 Jun '16

07 Jun '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 See this posting for context: https://lists.torproject.org/pipermail/tor-project/2016-April/000223.html Notes for June 2 2016 meeting: Alison: 1) status of community documents 2) still working on SIDA proposal with Isa Mike: 1) Postponed my vacation for another week or so to help with community issues. I'll be quietly working on my phone prototype in the meantime. 2) Will be attending a panel on the Decentralized Web next week. Then maybe vacation? Unclear. Shari: 1) Erin the new HR person starts on Monday, so I'll need help from various folks to get her set up. 2) Board meeting recap. Nick: 1) Changed addresses on many online accounts. Make sure everybody in the office knows how not to get phished. Karsten: 1) Released DescripTor 1.2.0 containing a complete rewrite of docs into Javadocs. 2) Finished metrics proposal together with Cass, Isabela, iwakeh, and Shari. Kate: 1) It's important that Tor people talking to the media about Tor touch base with me prior to interviews so that I can help them with media training (if needed), discuss the reporter with them, etc. I need to understand which reporters are covering which topics. This is an evergreen request and also a longstanding policy. Georg: 1) Tor Browser 6.0 is out \o/ Isabela: 1) network team - working on next release [make it smaller] 2) OTF - reply to their questions [also pinged Sue on invoices we should be doing will ping her again is $ to come in ;)] 3) DRL- preparing F-indicators and extension letter -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXVrBAAAoJEC3ESO/4X7XBFpsH/2Olfmnra7LFD4rjQ0rW5SK6 mexUJK+BuDagpIRj/96rZyWZAYXrVSND3p4ECMf/elOZqdZrZ04CNkrxyMRRIZBU m5Wl+T/pyJxowPv9nE7jgmkwM+156ZfMkJmqKC6NK9j52BY14C05p8Ni5c3IfPbg kjW8kNKx9apBnxbA+dhnTq9rHzNbvEDzNc1FhowVr1nsxHOevQwl+SPHdluJ5PoA PyP4Ux/qKtm0chumd1NPxh9I1WvZXXUdq2UwfWcfez3dWmepl+WCEy6mGRdpJ9TF bMlHKpaCN6xh0MC8fGGYX+WjDFHAjPHyW7gO+15NOTFVl7DSLUk3NUGkuW3Mh5Q= =/6x0 -----END PGP SIGNATURE-----

1 0

Hewlett Foundation Grants
by Tom Ritter 06 Jun '16

06 Jun '16

Someone pointed out the Hewlett Foundation grants to me: http://hewlett.org/blog/posts/refining-our-cyber-initiative-grantmaking-str… http://hewlett.org/sites/default/files/Cyber%20Initative%20Refined%20Grantm… It does not seem that they have 'open' grant applications, but they fund in the hundreds-of-thousands of dollars range to orgs like Berkman, New America, CDT, and a bunch of universities - so it seems worthwhile to think about and see if Tor could put in a proposal...? The goals for their grants are: - Building Capacity of Civil Society Orgs - Building Capacity of Individual Decision-Makers and Influencers - Building a Robust Network of Cybersecurity Experts - Generating Policy Driven Research and Thought Leadership - Cofunding It's not a slam dunk for the main sort of work Tor does, but it seems like it may fit OONI quite well or could be a vehicle for sponsorship of devs to attend things like Open Web Summits. -tom

1 0

Proxy Blocking Latency (preprint)
by David Fifield 01 Jun '16

01 Jun '16

Lynn Tsai and I, with the help of others, have been measuring how long it takes for Tor Browser's default bridges to be blocked. https://arxiv.org/abs/1605.08808 (click "PDF") Abstract: Censors of the Internet must continually discover and block new circumvention proxy servers. We seek to understand the pace of this process, specifically, the length of the delay between when a proxy becomes potentially discoverable and when the censor blocks it. We measure this delay by testing the reachability of previously unseen Tor bridges, before and after their introduction into Tor Browser, from sites in the U.S., China, and Iran, over a period of five months. We find that China's national firewall blocks these new bridges, but only after a varying delay of between 2 and 18 days, and that blocking occurs only after a user-ready software release, despite bridges being available earlier in source code. While the firewall notices new bridges in Tor Browser, bridges that appear only in Orbot, a version of Tor for mobile devices, remain unblocked. This work highlights the fact that censors can behave in unintuitive ways, which presents difficulties for threat modeling but also opportunities for evasion. The best summaries are on pages 4 and 5, which show in graphical/tabular form the dates of releases and how long the bridges remained reachable after. We would appreciate any comments or corrections. In particular, the description of the Tor Browser release process could stand some fact-checking by a Tor Browser developer.

2 2

Fwd: Applications extended - APNIC Internet Operations Research Grant
by Virgil Griffith 31 May '16

31 May '16

This seems like a lovely grant opportunity for someone doing BGP or traffic analysis work. Must have some presence in Asia Pacific. -V ---------- Forwarded message ---------- From: *APNIC Secretariat* <apnic-no-reply(a)apnic.net> Date: Tuesday, 31 May 2016 Subject: Applications extended - APNIC Internet Operations Research Grant ________________________________________________________________________ APNIC Internet Operations Research Grant applications extended ________________________________________________________________________ APNIC is pleased to announce that applications for the APNIC Internet Operations Research Grant have been extended by TWO WEEKS to 15 June 2016 (23:59 UTC). Applicants can apply for funding between AUD 5,000 to AUD 45,000 for research projects on topics related to Internet operations, infrastructure and related protocols, for example: - Network measurement and analysis - IPv6 deployment - BGP routing - Network security - Peering and interconnection Apply now --------- If you have a project that supports the development of an Internet research community whose results can improve the availability, reliability and security of the Internet in the Asia Pacific, then apply now. We encourage members of Network Operators Groups, members/partners of IXPs, operators of root servers, and academics and postgraduate students to submit their proposals. The APNIC Internet Operations Research Grant is administered and managed by ISIF Asia. For more information, please see: http://isif.asia/grant ________________________________________________________________________ APNIC Secretariat secretariat(a)apnic.net <javascript:_e(%7B%7D,'cvml','secretariat(a)apnic.net');> Asia Pacific Network Information Centre (APNIC) Tel: 61 7 3858 3100 PO Box 3646 South Brisbane, QLD 4101 Australia Fax: 61 7 3858 3199 6 Cordelia Street, South Brisbane, QLD http://www.apnic.net ________________________________________________________________________

1 0

Tor Hackfest during HOPE?
by Kate 30 May '16

30 May '16

Hi, David Huerta is founder of NYC's hackerspace Resistor and has a very cool day job helping to envision the future of libraries (first locally and then nationally), at the Brooklyn Public Library. He wants to host a Tor hackfest during HOPE. Cheers, Kate Hello, re: latest blog post: https://blog.torproject.org/blog/mission-montreal-building-next-generation-…. Would there be any interest in a Tor Hackfest in NYC? I can bounce the idea off the other NYC Resistor (http://www.nycresistor.com/) kin to see if we can schedule a day or two for late July; Same week as HOPE? We can host groups < 25 people, pro bono. Let me know if there's any interest, .dh huertanix(a)nycresistor.com

3 2

Notes from May 26 2016 Vegas team meeting
by Karsten Loesing 30 May '16

30 May '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 See this posting for context: https://lists.torproject.org/pipermail/tor-project/2016-April/000223.html Notes for May 26 2016 meeting: Georg: 1) Tor Browser 6.0 is ready for QA. Planned release day is May 30. 2) I worked on our search engine problem. Disconnect switched the fallback to DuckDuckGo. 3) I reviewed 2 papers Nick: 1) Tor 0.2.8.3-alpha is almost out. Which TorBrowser will get it? 2) Talked with some folks and Isabela about doing an audit on the Tor code. (Roger set this up; I think an existing funder would be paying?) Seems promising so far. 3) Had meeting with Isabela and team. Productive but team feels stretched. IMO we need: * A sense that everybody is doing their fair share * Nearly all people to be contractually 'allowed' to work on nearly all things. * To track non-coding tasks as well a coding tasks when planning time and allocating people * A better sense of how much volunteers would like to commit, and a way for us to be able to ask the paid people before the volunteers. We have planned to: * Get a working code review system * Add review-points to trac * chop 0.2.9 and future releases down to size * improve our workflow. * have another meeting in july Kate: 1) Rule 41 update —Need to stay with bipartisan talking point: DOJ is trying to get a major policy change enacted with a rule change in the Federal Rules of Criminal Procedure--DOJ is trying to circumvent Congress. Rep. Poe's office is introducing co-sponsors in two's-- one democrat for each republican. It's going well. 2) CloudFlare update: More allies are joining us; we are planning to track CloudFlare's promises and hold them accountable, probably via an email list. 3) A-Clinic Collaboration - probably not a formal collaboration with this foundation that wants to use onion services to do anonymous health surveys, etc. A letter describing our involvement is still being negotiated. 4) Recruited volunteers to help with HTML tagging so we can upload more things to the Tor website. 5) Press Kit: Volunteer David Stanton is working on user stories document and I am finishing onion services doc as well as document that describes myths about Tor and explains the realities. 6) US Mission in Uganda held an Internet freedom and human rights Twitter event - we participated (5/26) We received some media coverage about the onion services hackfest, including a nice SlashDot piece - BoingBoing: https://boingboing.net/2016/05/26/tor-project-is-working-on-a-we.html - The Register:http://www.theregister.co.uk/2016/05/25/nextgen_tor_to_use_distributed_rng_55character_addresses/ - Softpedia: http://news.softpedia.com/news/tor-to-use-never-seen-before-distributed-rng… - IBTimes: http://www.ibtimes.co.uk/tor-develops-its-own-random-number-generator-make-… - Hackread: https://www.hackread.com/tor-developers-next-gen-onion-service/ - Slashdot: https://yro.slashdot.org/story/16/05/25/2347238/tor-to-use-distributed-rng-… - Naked Security: https://nakedsecurity.sophos.com/2016/05/26/tor-takes-on-the-question-what-… FBI is being pressured by the judge to release Tor 0-day in Washington State case Shari: 1) board meeting on Friday; anything you want me to bring up? 2) Monday is a holiday in the U.S. How to handle holidays? 3) Personnel update. Isabela: 1) Organized retrospective meeting with the network team for the team to have a sense of how things are going and where are the pain points we need to improve. Went pretty good for my first irc retrospective :) 2) Working with Alison on updating the SIDA proposal. 3) Working on possible Mozilla grant - at first with TBB and Nathan because we were thinking of applying for mobile browser - now with Karsten because we probably will apply for metrics instead per Mozilla's feedback. 4) focus on making the release 0.2.9 smaller / pick up DRL work (M&E and F-indicators and extension) are the things for me starting next week Mike: 1) I'm wrapping up the last thing before I take a vacation: I'm going to help with the Mozilla proposal(s), and then start my vacation, ideally on June 1st. Karsten: 1) Continued writing a funding proposal for metrics work, together with Isabela and Cass who have been extremely helpful so far. Deadline is May 31st. 2) Just talked to weasel about the virtual machines at one of our hosters basically falling apart. We'll need to migrate them ASAP to a new hoster. Apparently, budget shouldn't be an issue there, because we're freeing up some money by reducing hosting elsewhere, but just in case there's overlap we might be paying a few hundred USD extra. -- Asked Shari for ~200 USD/mo, which she approved. Alison: 1) social contract draft is with Lunar and Matt for one more review before Vegas leads 2) the community council is writing our guidelines -- still in its very early stages 3) sent another update of the membership doc to this team for review - -- next it'll go to tor-internal@ 4) reworking SIDA proposal with Isa 5) OTF concept note for building community capacity within Torservers was invited for a full proposal! 6) Cloudflare meeting (Mike will probably update) 7) support team met yesterday. we hope to integrate this team more into the community team. phoul has done major updates to the support docs and we're now working on plans for distribution and translation and maintenance. -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXTAaJAAoJEC3ESO/4X7XBO5oH/3FH9ZW7O1aJwkIl0vByaPP9 JXDosBBm2FssksZn9z498qQ7o6HkSlfrO0oT3nnjvQlteYGZZQj+gdDuFpiQ8KTD tKlUk753iWDgPrsK0+WMszhKYpe/zNIOQ7GieY0Xx3Nkxmzvc/buMlxA+qHkF09/ NFv6WqJUTy3nZsf8N8JwD2pUiFafXLzthEmrGgLsHxNsIFN1BbdI4npZIueV0Cpw 1cQk01eZKZtoDi03/ilAsVtUoeBYRmjktUgdFIAh9vXputAfG7pgliJCbxj2j+Dw k8p7HfjJQsgistQJJrLVus9Tt1rYQULDqw0r2G9cn6dhuO/zBSNJNBJeqgWH+hE= =FVjF -----END PGP SIGNATURE-----

1 0

Fallback Directory Monitoring
by Damian Johnson 29 May '16

29 May '16

Hi Tim, hi Nick. As requested on ticket #18177 [1] we now have a new DocTor monitor [2] that checks the reachability of our fallback directories. A notification that looks like the following is sent to the three of us and #tor-bots if over 25% of the fallbacks are unreachable... ------------------------------------------------------------ 29/100 (29%) fallback directories have become slow or unresponsive... * 9504CB22EEB25D344DE63CB7A6F2C46F895C3686 => IPv6 ORPort is unreachable (2a03:b0c0:3:d0::2ed:7001:9050) * AEA43CB1E47BE5F8051711B2BF01683DB1568E05 => IPv6 ORPort is unreachable (2001:41d0:a:74a::1:443) * 8B7F47AE1A5D954A3E58ACDE0865D09DBA5B738D => DirPort is unreachable (178.217.184.32:9030) ... etc... ------------------------------------------------------------ A fallback is defined as unavailable if... * We can't connect to its ORPort. * We can't connect to its DirPort. * We can't connect to its IPv6 ORPort (if it has one). * It takes longer than 15 seconds to provide the consensus (download times are usually ~3s). The cron runs once per day. Happy to also send these to tor-consensus-health@ if anybody there wants the notices. Cheers! -Damian [1] https://trac.torproject.org/projects/tor/ticket/18177 [2] https://gitweb.torproject.org/doctor.git/tree/fallback_directories.py

1 0