July 2017 - tor-project - lists.torproject.org

Fwd: Cybersecurity and cryptography ebooks in our new bundle!
by Shari Steele 17 Jul '17

17 Jul '17

Hey all. Name your own price for cybersecurity and cryptography ebooks! And while I love EFF (one of their chosen charities), I encourage you to choose "select a new one" and then do a search for Tor Project. You can always select us in this way for any Humble Bundles you purchase. Shari > Begin forwarded message: > > From: "Humble Bundle" <contact(a)mailer.humblebundle.com> > Subject: Cybersecurity and cryptography ebooks in our new bundle! > Date: July 17, 2017 at 11:22:36 AM PDT > To: ssteele(a)eff.org > Reply-To: contact(a)humblebundle.com > > <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> > <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> > Pay what you want for a bundle of ebooks on > cybersecurity, hacking, cryptography & more! > <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> > Secrets and Lies: Digital Security in a Networked World, Applied Cryptography, The Art of Deception, Social Engineering, and other great titles from Wiley > Get it now! <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> > Supporting: > <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> > Pay what you want for a bundle celebrating comics greats Kirby & Eisner! > <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> > Check it out! <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> > <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> <https://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca…> <http://track.cordial.io/c/102:5969310af4ab4ee605cf8d98:ot:56c3e4e8733462ca8…> > > This email was sent to ssteele(a)eff.org <mailto:ssteele@eff.org> > unsubscribe from this list <https://track.cordial.io/optout/index.php?mcID=102:5969310af4ab4ee605cf8d98…> | update your preferences <https://www.humblebundle.com/newsletter-update?id=56c3e4e8733462ca89422378> > © 2017 Humble Bundle Inc. | 201 Post Street 11th Floor | San Francisco, CA | 94108 > >

1 0

Notes from July 13 2017 Vegas team meeting
by Karsten Loesing 14 Jul '17

14 Jul '17

Notes for July 13 2017 meeting: Arturo: 1) We ran the OONI Partner gathering in Toronto and it went well. 2) Now attending CLSI where we have many OONI Sessions Alison: 1) About to submit the Sappi graphic design grant for making LFP posters 2) Need to start creating the schedule for the Tor Meeting 3) Working on code of conduct draft with Catalyst 4) Putting finishing touches on support wiki, writing blog post for it 5) Organized meeting for support team 6) A few members of the community team lost a bunch of data stored on Sandstorm, appears to be unrecoverable :( 7) Phoul continues to work with Trusteer to solve issues with blocking Tor Browser/Firefox ESR 8) I'd like to start organizing the Tor meeting schedule next week sometime. Karsten: 1) Put out CollecTor 1.2.0 release, started working on 1.3.0, to be released by end of the month. 2) Worked on a specification of sanitized bridge descriptors. 3) Will be working on MOSS final report and blog post over the next very few weeks. Isabela: 1) Reports and invoices: finished june report for sponsor4 - sent out last invoice for MOSS, got back from them a request for final report and blog post Brad: Is Sponsor 4 ready to invoice now? 2) Working on NSF reports - met with Brad yesterday - got a little blocked because of storm issue but started working on pads for each NSF grant to collect report information. 3) working with Linda on website redesign - preparing the tpo information architecture doc so we don't loose track when building wireframs. We got comms team looped in in the project now. For July Linda will continue to work on the website wireframes+organzing content/functions; update tor launcher wireframes and organize user testing for onion browser onboarding project 4) working with hiro on issue tracker 'benchmarking' table (requirements from survey, vs gitlab and trac has to offer). Hiro is also working on the grant pipeline form and on remaining tor blog tasks. 5) long pending stuff that i never get to finish - tor launcher feature brief update, growth strategy update - hope to get to those :( [Sandboxing planning, Tor Messenger strategy; just two things that might be missing on your list :) GeKo] ! true and PT POC 6) will be at PETS next week o/ Steph: 1) Preparing for bug bounty launch: Tor blog post, H1 q&a blog post, coordination with H1 on press outreach, OTF will support on social media. Projected launch date: next Thurs 2) Finalizing newsletter, will likely send by Tues. Running a lot of tests with Civi 3) Upcoming content: bug bounty, safety hierarchy of diff ways to access Tor, Tor 6 mos metrics, sha2017 4) Tommy and I have joined website redesign convo, adding commments. Copy to come later 5) Maintaing consistent posts on FB (at least 1/day), twitter (3-6/day), linkedin (1/week). Analytics up over the past month. Nick: 1) All's well with the network team afaict. 2) Trying to get everything straightened out with timesheets, expenses, etc. Thanks to Brad and Sue for all their help! (Am I supposed to confirm that expenses/travel were preapproved?) Brad: I verify proper approval before we issue expense reimbursement. No need to confirm on your end, but please note any concerns you have re: lack of proper approval and/or potentially unallowable charges during your review (Nick: Thanks, Brad!) 3) Roger -- please look at Taylor's notes wrt sponsor3 and let us know if we're on the wrong track? 4) Done with massive ticket triage and labeling on tor: unspecified. Started to sponsor-label some of our tickets 5) At PETS next week. Georg: 1) I Helped with the bug bounty launch planning 2) I worked on moving the browser dev hiring forward (we are almost ready to start with the coding tasks) 3) Isa -- Where are we with the job postings for the mobile work? [Question: would the description of the current browser dev be the same for the mobile work?] [not exactly. we could certainly reuse parts but we need to add mobile specific things (knowledge of Java might certainly be a good thing; experience with mobile development as well etc.)] 4) Did we figure out the timesheet management questions? <- we are still working on it Brad: 1) Closing the books and performing final review for fiscal year-end 2) Completed final steps of conversion to ADP for US-based payroll processing (first paycheck is July 14) 3) Updating grant/contract sub-ledgers to reflect budget-to-actuals through June 30 4) Gathering info to assist arma with annual reports due for Sponsors M, V, 2 & 3 6) Creating detailed travel budget for Montreal meeting based on invite lists 7) Working with Jon to overhaul spreadsheet he uses to track attendees for Montreal meeting 8) PETS meeting next week: should we expect to receive any large invoices that are to be paid out of TPI's PETS fund? Mike: 1) Helping with the Tor Browser hiring 2) Emailing researchers about changes to padding code and fixing bugs 3) Meeting with folks at PETS next week Shari: 1) Lots of loose ends requiring bits of my attention. 2) Working on final report for donation database. 3) Worked with Jon to get invitations out; can we send the last ones? 4) Answering lots of questions for MDF general operating grant. 5) I have to answer DRL questions. 6) mikeperry, did you see my email about Mozilla/Amazon? Please respond to it about whether you'll be around to help!

1 0

Update from Tor's Community Council
by Jens Kubieziel 13 Jul '17

13 Jul '17

Hi friends, I am writing on behalf of the Community Council with some updates. We wanted to be in touch and let folks know what we have been up to since the recent election. We have had several meetings with the new Council (Alison, qbi, Linda, Hiro, Gunner). We are enjoying working together. In the near term, we are prioritizing the drafting of policies and procedures for the Council. Our plan is to draft these sequentially and then ask for community input once we think specific policies and procedures are ready for feedback. Procedures we are drafting include case handling, Council operations (e.g. when and how we meet), and Council elections. Policies we are drafting include conflict of interest, operational security (in particular what we store and where), and confidentiality (what is and is not confidential). We welcome anyone interested to reach out to any or all Council members if you have input, questions or concerns you would like to share We'll continue to update the community at least once a month. thanks, -- Jens Kubieziel http://www.kubieziel.de Weisheit ist mehr als Wissen: Es kommt darauf an, was zu tun ist, und nicht, was zunächst getan werden soll. Herbert Clarke Hoover

4 4

Core Tor sponsor 4 June report
by isabela 12 Jul '17

12 Jul '17

In June we finished the task [1] to update dir-spec.txt to reflect prop278. We continue to run tests, compare measurements and fixed bugs, some were found at our test network, and an important one (more bellow) affecting other tor relays. Some of the bugs we diagnosed and fixed: #22460 Link handshake trouble: certificates and keys can get out of sync [2] #22466 "Crosscert is expired" warnings: RSA->Ed25519 identity crosscertifice apparently made in 1970? [3] #22751 LZMA coder causes crash when the sandbox is enabled [4] #22752 Assertion failure in consensus_cache_entry_handle_get on Windows [5] As mentioned, we found an important bug that cost us some time to figure out. This was related to the implementation of both proposals, 140 and 278. Where we didn't send the "not modified" header so relays would keep asking for data they already had and receive the document. This was leading to more bandwidth usage which is completely the contrary of our goal with this project. The bug was tracked under this ticket: #22702 Never send a consensus which the downloader already has [6] We collected measurements before and after fixing the bug [7]. If you look at our spreadsheets, in the "regression found" subsheet you will see that middle nodes (XXXm under ID) and relays (XXXr under ID) are above 100% in the delta, which is a regression (using more bandwidth). In the "regression fixed" subsheet, you can see that for XXXm and XXXr nodes this is fixed. They are around 55% which give us a bandwidth improvement of 45% for relays. For clients we ave reduced the bandwidth consumption to the point where we are now only using 41% of the bandwidth we used before version 0.3.1 of core tor. We are very happy with these results. For next month we will evaluate one more compression algorithm to see if we can improve these gains even more[8]. And we also received a ticket[9] from an user (relay operator) with a low-powered machine complaining about a side effect our solution have created. Where a relay now generates a bunch of diffs every time it gets a new consensus, and then it compresses them all in several ways, this happens in the background, but for low-powered machines is noticeable as it's taking a lot of resources. We have a couple of design changes to solve this in mind and will be working on it in July as well. [1] https://trac.torproject.org/projects/tor/ticket/22275 [2] https://trac.torproject.org/projects/tor/ticket/22460 [3] https://trac.torproject.org/projects/tor/ticket/22466 [4] https://trac.torproject.org/projects/tor/ticket/22751 [5] https://trac.torproject.org/projects/tor/ticket/22752 [6] https://trac.torproject.org/projects/tor/ticket/22702 [7] https://docs.google.com/spreadsheets/d/1l_m-kHkOrq4UGmTUtpuffbUY85fvcDQJaoF… [8] https://trac.torproject.org/projects/tor/ticket/22819 [9] https://trac.torproject.org/projects/tor/ticket/22883

1 0

Damian's Status Report - June 2017
by Damian Johnson 12 Jul '17

12 Jul '17

Short one this month but here ya go! http://blog.atagar.com/june2017/

1 0

Default obfs4 bridges frosty and dragon reporting 0 bandwidth since ~June 18
by David Fifield 10 Jul '17

10 Jul '17

These bridges, added to Tor Browser in ticket #22468, are reporting 0 bandwidth since a few days ago. Is there something wrong with them? https://atlas.torproject.org/#details/854173307E33686BBBAC36A3A093BEF320B71… https://atlas.torproject.org/#details/D9E712E593400635462172121B7DB90B07669…

1 1

Community Team report June 2017
by Alison 10 Jul '17

10 Jul '17

ello all, Here are the highlights of the Community Team's work in June 2017: June 2017 Community Team report Meeting notes June 2017 ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Tor Meeting planning ================================================================== Alison began planning for the October Tor Meeting in Montreal. Invites will go out very soon! Windows 10 user issue ================================================================== Alison and Phoul identified an issue that was preventing Windows 10 users from opening Tor Browser when they were also using a popular piece of banking software. Phoul was able to get the issue resolved, but this problem has occurred with past versions of both pieces of software, so we are working with the makers of the banking software to prevent this problem in the future. Community Team roadmap ================================================================== We're roadmapping our plans for the rest of 2017 and trying to coordinate our dependencies with other teams, particularly dependencies related to user support. Support portal/support wiki ================================================================== The full support portal has to be put on hold while we wait for an update on that funding, so we've opted to put the questions and answers onto a read-only wiki so that users have something to help them in the meantime. We'll publish the wiki in July with a blog post announcing it. Contributor guidelines ================================================================== Alison, atagar, and arma put the finishing touches on our core contributor (membership) guidelines draft, and arma initiated the proposal discussion on tor-internal at the end of June. Library Freedom Project ================================================================== We completed and submitted the IMLS grant at the beginning of June. We then began working with a graphic design firm on another grant to make infographic posters explaining basic privacy concepts, like encrypted messaging and strong passwords. If we get this grant, we'd print the posters in at least three languages (English, Spanish, and Arabic) and distribute them for free to any interested libraries. Outreach ================================================================== sukhe made plans to give two Tor talks in Toronto in August: https://lists.torproject.org/pipermail/tor-community-team/2017-June/000048.…. He also connected with folks at SFLC India and is working on some talks with them in September. Phoul, Alison, arma and others participated in the Localization Lab AMA. ================================================================== Next up: completing the community team roadmap, more meeting planning including the Montreal meeting and future Global South meeting(s), publishing the support wiki, drafting the code of conduct, writing documentation for FOSS/Tor cultural norms for onboarding new employees, organizing support team feedback to applications team. ================================================================== Thanks for reading! -- Alison Macrina Community Team Lead The Tor Project

1 0

GSoC 2017 - unMessage: Report #3
by Felipe Dau 07 Jul '17

07 Jul '17

Hi everyone! This is my report #3 for the unMessage GSoC project. # Updates Since the last report I mostly worked on making methods asynchronous using `Deferreds` and `@inlineCallbacks` (task #21 [0]), but also on learning how to properly use Twisted's reactor, which will be important for the tests (task #33 [1]). # What's next Continue working on these tasks to have new tests running soon. Thanks, -Felipe [1]: https://github.com/AnemoneLabs/unmessage/issues/21 [2]: https://github.com/AnemoneLabs/unmessage/issues/33

1 0

GSoC 2017 - Crash Reporter for Tor Browser: Report #3
by Nur-Magomed 07 Jul '17

07 Jul '17

Hi everyone! This is my bi-week status report for GSoC project "Crash Reporter for Tor Browser". # Crash Reporter Client: - added feature: blacklist to remove privacy-sensitive fields from reports[1]; - few updates in project-wiki [2]. # What's next Now work is focused on Socorro (crashreporter server side): adapting Socorro Collector (software that gets crashreports from clients) for changed crashreports. And, cypherpunks, thank you for ideas and editions in project-wiki [2]. Kind regards, Nur-Magomed [1] https://github.com/nmago/tor-browser/commit/613e9c65426ee448d8c2dcefbf32ed7… [2] https://trac.torproject.org/projects/tor/wiki/doc/crashreporter

1 0

GSoC 2017 - anon-connection-wizard: Report #3
by iry 07 Jul '17

07 Jul '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello Tor people! The following is my bi-week status report for the anon-connection-wizard project. # anon-connection-wizard development ## features implemented - - switched from edit mark approach to torrc.d approach - - integrate anon-connection-wizard with the upcoming whonix14 ## features improved - - remove "advance" button on the main page ## links - - detailed discussion[0] [1] - - commits on Github [2] # torrc.d related work - - posted a feature request against Debian tor package on Debian BTS [3] - - tried to keep up with the torrc.d implementation process [4] # Next step - - torrc.d is a really important feature. I will see what I can help to make it available sooner. - - more testing on the integration with whonix14 - - investigate on how to successfully package it by "make deb-icup" - - use python's temporary directory features instead of .tmp which was created by myself - - continue polishing anon-connection-wizard and implement new features Thank you! Best, iry [0]: http://forums.kkkkkkkkkk63ava6.onion/t/graphical-gui-whonix-setup-wizard - -anon-connection-wizard-technical-discussion/650/280 [1]: http://phabricator.kkkkkkkkkk63ava6.onion/T699 [2]: https://github.com/irykoon/anon-connection-wizard/commits/master [3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866187 [4]: http://forums.kkkkkkkkkk63ava6.onion/t/torrc-d-is-comming/4041 -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZX7d+AAoJEKFLTbxtzdU8sDwP/jIqXzhR7sHBcmseogmYxlu7 RnSz20JjhG5UCTALntk9czblThDfZhd6/oUdq7UrdXzEXDIjGfExM6OYkWOiIoAW 02q3d0eXtjMXJ5YwGe69AbiV0IaUeQJ5Hp/02/UmD3wnJK9nmNXA6Lo9cfVaEnif b+dt3zAPZpuJo8XNlNd2bG6+qA6qKVKu2FVvtYkogJCrkN18rZ/qXZki8y6hxjIA TVQ0JupbXrTzogT9aMFnAL8Qwndh+B4mVDpmI5AfRyEIMxJ0VDjFZylfypQHMTnk 4GQg22wCALdDzorbuzCQjfU6NKsUz3B4URi1XkamlSvytJaaceqZpfArTJ8/fGJm o3z2j+BnA3WvGMkX2VNPlJKugXlE5dwqFChJz0snLTKs5IQPbU9ImD1g327BXZAn 39WTGUh57c0r2p9auo8G/JJdczx6SAtnqeyogtIA8uXKKilDHPfY1adpBEBg3OMX Nk5C9jEyv/qPT+IitHRaukWWWZ1abH752caCQ7UKVzSj/UWrSE3k8A9vZ6u16UX+ TPc5Yzl3uwJ5Ny7hmeQ42RcSpw3XhOGHpXZ7FVag9rTXewHzJojj0NuF1gao7mDG kJmFc3Rn0ZU3Ueu0BIqLBrQpnYBsx93Zw5xLrx8Tkoy3gilwTAkUsEDYaJrwuLHQ KYxbSTEETvk73dZgiH1z =62jH -----END PGP SIGNATURE-----

1 0