Hi,
Between 22 and 30 March, the Tor Project will host the second edition of
our user documentation hackathon, the DocsHackathon. The DocsHackathon
is a totally remote and online event.
If you've never volunteered with us before, this is an opportunity for
you to become involved in the community, get closer to our work, and
make meaningful contributions. During our first DocsHackathon last
September, we had 70 registrations, 8 contributors, and over 70 pull
requests to the support portal, Tor Browser manual, our main website,
and other repositories. If you helped out last year, we hope you can
join us again or help spread the word. Once the DocsHackathon is
completed, we'll reward the top 3 contributors with official Tor swag.
So if you're a copywriter, front-end dev, tester, or content reviewer,
we'd appreciate your help improving our documentation, updating our
support portal, and ensuring their relevancy. Don't feel like any of
these apply to you but still want to help out? Chat with us on IRC
(#tor-www - irc.oftc.net) or the community team mailing list to join us
and find out where you could add value.
Read more here:
https://blog.torproject.org/docshackathon-2020
And here:
https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/DocsH…
all the best,
Gus
--
The Tor Project
Community Team Lead
http://expyuzz4wqqyqhjn.onion/
Hello!
Here comes the summary of our weekly network-health meeting we hold
yesterday in #tor-meeting. The IRC log can be found at:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-16-18.59.log…
The items from our pad (both discussion and status related) can be found
below:
Discussion
==========
- strategy for moving #32672 forward (pinging relay ops on social
media etc.) [GeKo: we decided to have two social media campaigns/pings:
one now that the patch for that ticket got merged and one once it is
about to reach a stable release. ggus is working on that. GeKo is
talking to the network-team folks about a timeline for getting the patch
backported]
Statuses
========
GeKo:
Last week:
- more sbws work
- #32864 (I wrote a script to parse the JSON output and contacted
affected operators)
- got back to EFF for the legal questions update
- looked again at #33361 for review
This week:
- more #32864 (further testing and tweaking new script and
bad-exiting first relays)
- more sbws work (#33599, #33009)
- start work on exit relay blocking problem by large websites/CDNs
etc. (#33500 etc.)
- start looking closer at bad relay scanners we have and issues that
have accumulated (#33180, #33181)
juga (probably offline):
Last week:
- Continued with child of #30719: #30905 (change state values when
sbws is restarted)
- Had voice meeting with GeKo and ahf (separately), we decided or
commented:
- to have regular meetings the 3 of us together (so nice to talk
by voice!)
- to report back in the network-health weekly meeting
- migrate trac to gitlab.tpo soon, migrate remaining tickets in gh
to gitalb.tpo, make reviews in gitlab.tpo
- we will run longclaw bwauth with last maint-1.1 branch to be
able to detect bugs before migrating all bwauths to sbws, since
currently we don't have a way to test sbws as it'd run for several days
and doing so would require quite more time
- i'll make minor changes in #30905 (not just bugfixes) because i
don't think there's currently a way to know when things happened storing
only numbers
- general overview and history of sbws (why things are like they are)
Next week:
- Continue with #30719
- Continue with #30735
gus:
this week:
- Tweet about 0.2.9 and 0.4.0 patch
Georg
Hello,
Here is a short summary of the network team meeting from Monday the 9th of
March 2020.
1) We started out with roadmap.
2) Reviews seemed alright.
3) We went over our 0.4.3 status page.
4) We discussed if we should do post-TROVE retrospectives. We should discuss
that at our next retrospective.
5) To focus on S55 Teor has dropped some tasks that the rest of us should be
better at keeping up with if we have capacity for it.
6) We discussed a queue system for topics for our larger team voice meetings.
7) Nick asked if there was any objections to using CBOR for Walking Onions.
8) Nobody had anything else to discuss.
--- end of summary ---
You can read the network team meeting log at:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-09-16.59.html
Below are the contents of our meeting pad:
Nick:
Week of 2 Mar (planned):
- Start on walking onions spec work:
- Write a working schedule
- Identify areas of uncertainty, start investigating them.
- Start outlining proposals
- Speaking at a workshop about decntralized web stuff on Wed, possibly Thu.
- Team retrospective on Tuesday, right?
- Finish all peer evaluations
Week of 2 Mar (actual):
- Started on walking onions spec work. Made LOTS of progress. See https://lists.torproject.org/pipermail/tor-dev/2020-March/014178.html for details
- Spoke at workshop on Wednesday. Was interesting and met good people; not sure if I should have spent a full day.
- Wrote peer evaluations
- Updated HS config refactor branch
- Review and merge
- Peer feedback evaluations
Week of 9 Mar (planned):
- Continue work on walking onions spec:
- Write initial draft spec for ENDIVE and SNIP formats.
- Schedule the rest of the work
- Prepare for new stable and alpha releases, targetting 16 March:
- Finalize TROVE fixes?
- Write draft advisories, get comments
- Review and merge
- Send an email to grants@ about stuff we should seek funding for.
- Draft bug retrospective notes, using https://pad.riseup.net/p/tor-bugs-retro-042-keep as input.
- Meetings: library size work (monday), NY meeting planning (thursday??)
Currently postponing on:
- progress on C autoformatting
- 043 tickets, including some that seem important:
- Build issue 33437
- Windows issue 24857
catalyst:
week of 03/02 (2020-W10) (planned):
- retrospective 03/03
- catch up on reviews
- write feedback
week of 03/02 (2020-W10) (actual):
- reviewed #32921, #33460
- retrospective 03/03
- wrote some feedback
week of 03/09 (2020-W11) (planned):
- reviews
- refresh expired PGP key on various infrastructure
- finish writing feedback
ahf:
Week of 2/3 2020 (planned):
- Talk about Tor Browser at the Engineering Union here in DK on Thursday. Will be AFK some of that day DK time, but online in the evening.
- Retrospective
- Work on Git migration to new GL instance
- Start merging peer review.
- Lots of discussions.
- Slightly behind on reviews. Planning on catching up on that Friday.
Week of 2/3 2020 (actually):
- Had retrospective.
- Did talk at the Engineering Union.
- Tracked incoming peer reviews from network team folks. I have everything now from everybody! Thanks.
- Caught up on reviews.
- Continued GL migration work, but still not on the new instance yet.
Week of 9/3 2020 (planned):
- Focus on TROVE and Windows CPU issue with cache dir (#24857).
- Try to close IRC and email a bit this week to focus :-)
asn:
Week of 02/03 (actual):
- Reviews
- Peer feedback
- Did another call for testing for OBv3.
- Worked on HTTPS-Everywhere S27 deliverable.
- Worked on onion services DoS meeting planning.
Week of 09/03 (planned):
- Finish CI work for OBv3.
- Write blog post for OBv3 testing.
- Prepare packages for OBv3.
- More planning for DoS stuff.
dgoulet:
Last week (actual):
- Review and merges.
- Wrote feedback reviews
- DoS meeting logistics
- Spent some times figuring out #33491.
Week of March 9th (planned):
- Tor binary and library size meeting. Some work will probably spawn from
that.
- Planning for DoS meeting. Meeting on Wed. for that.
- A series of tickets in the pipe that needs code: #33458, #33491, #32542,
#32910, #33072, #33400
Gaba:
Last week (actual):
- s30 check-ins
- s69 kick-off
- nyc traveling
Week of February 24th (planned)
- more nyc traveling
teor: (online first meeting of the month, offline at the usual meeting time)
Week of 24 February (planned):
(No plans)
Week of 24 February (actual):
Important:
- Emails and IRC
- Meetings
- Outreachy IPv6 project
- Feedback
- Network Health / Sponsor 55 Relay Proposal
Roadmap:
- (No progress)
Other:
- Ticket triage, backport deciding, quick code reviews and ticket help
Week of 2 March (planned):
(No plans)
Week of 2 March (actual):
Important:
- Emails and IRC
- Meetings
- Outreachy IPv6 project
- Feedback
- Network Health / Sponsor 55 Relay Proposal
Roadmap:
- (No progress)
Other:
- Ticket triage, backport deciding, quick code reviews and ticket help
Mike:
week of 19 Feb (planned):
- Investigate/reproduce circpad shutdown bugs (#30992 and chutney warns); plan some fixes
- Mull over Research Janitor responsibilities and priorites
- Maybe review metrics-team tickets
week of 19 Feb (actual):
- Still discussing Reasearch Janitor role priorities
- Performance funding proposal work
week of 24 Feb (planned):
- Cashing in some banked overtime dayz (Monday+Tuesday)
- Probably keep discussing Reasearch Janitor role priorities
- Performance funding proposal work
- Metrics-team flashflow experiment+sbws review
- circpad bugs I hope? Coin toss for that vs metrics-team review
(though the metrics work is pretty cold now anyway... maybe it can wait some more)
jnewsome:
week of 03/02 (2020-W09) (planned):
- Phantom design and prototyping
- Create Tor tickets for "build for shadow"
- Add nightly CI workflow to shadow repo to test against tor@head
week of 03/02 (2020-W09) (actual):
- Rebased Shadow-Phantom onto tip of Shadow-master and got CI passing again
(by disabling most of it)
- Solidified plan for Shadow-Phantom's interposition strategy, sent a PR to
use it and re-enable now-covered CI tests
- Sent out proposal for shared-memory-IPC plan
- Added a CI configuration matrix to shadow-plugin-tor to test against last
few releases of Tor
week of 03/09 (2020-W10) (planned):
- Flesh out Shadow-Phantom libc/syscall coverage to run phold (simple
network benchmark)
- Migrate shadow and shadow-plugin-tor to tgen v1.0.0
- Create Tor tickets for "build for shadow"
- Add nightly CI workflow to shadow repo to test against tor@head
All the best,
Alex.
--
Alexander Færøy
Hi everyone,
This is only a reminder that the weekly Tor Browser meeting is now held
at 18:00 UTC in #tor-meeting2 (on Mondays, as usual).
See some of you later today!
- Matt
Here is our meeting log:
http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-12-17.59.html
And here is our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Next meeting: Thursday March 19th 18:00 UTC
Weekly meetings, every Thursday at 18:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress).
== Goal of this meeting ==
Weekly checkin about the status of anti-censorship work at Tor.
Coordinate collaboration between people/teams on anti-censorship at Tor.
== Links to Useful documents ==
* Our anti-censorship roadmap: https://gitlab.torproject.org/torproject/anti-censorship/roadmap/boards
* Our roadmap consists of a subset of trac tickets. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1
* Next planning session: last week of April
* The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam
* Past meetings' notes can be found at: https://lists.torproject.org/pipermail/tor-project/
* GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proj…
* Tickets that need reviews: from sponsors we are working on:
* https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30
* https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28
-------------------------
--- March 12th 2020 --
-------------------------
== Announcements ==
* Tor participating in Google Summer of Code, ideas page: https://community.torproject.org/gsoc/
== Discussion ==
* obfs4proxy currently cannot build because of deleted dependency. how should we fix this short-term and long-term? #33464
== Actions ==
* Please help phw compile our monthly report by adding your highlights to this pad:
* https://pad.riseup.net/p/vGR0zvyXCuV3HG09VX-j
== Interesting links ==
* https://gfw.report/blog/gfw_looking_glass/en/
* Heartbleed-like memory disclosure (out-of-bounds read) in GFW's DNS parser. Worked circa 2010, doesn't work now.
* https://www.sciencedirect.com/science/article/pii/S0167404820300626
* "Protocol Proxy: An FTE-based covert channel"
* We present a proof-of-concept format transforming encryption (FTE)-based covert channel for tunneling TCP traffic through protected static protocols. Protected static protocols are UDP-based protocols with variable fields that cannot be blocked without collateral damage, such as power grid failures. We (1) convert TCP traffic to UDP traffic, (2) introduce observation-based FTE, and (3) model interpacket timing with a deterministic Hidden Markov Model (HMM).
* Open access copy: https://sci-hub.se/http://www.sciencedirect.com/science/article/pii/S016740…
== Updates ==
Name:
This week:
- What you worked on this week.
Next week:
- What you are planning to work on next week (related to anti-censorship work).
Help with:
- Something you may need help with.
Hiro: (last updated before 2020-01-09)
Started restoring Twitter Responder.
When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. <-- is this #27330 ?
Next Week:
- Work on gettor specs <-- Is this #3781?
- More with review of strings and website content and translation
phw:
This week (2020-03-12):
* Back from vacation and still catching up. Please let me know if you need me to prioritise something.
* Finished peer feedback.
* Created new info page on BridgeDB explaining our distribution mechanisms (#33008).
* Another round of analysis for the success rate of our new captchas (#24607).
* There's much more to study here but not enough time :/
Next week:
* Write a summary of our current BridgeDB distribution mechanisms and brainstorm new ones
* Pay attention to volunteer work (help agix with BridgeDB reviews; thymbahutymba with docker; Sergey with https proxy)
* Make BridgeDB report internal metrics (#31422)
* Catch up on RACE; in particular wrt obfs4 improvements
Help with:
*
Gaba: ()
Last week (2020-03-12):
* sponsor 30 coordination
* talking with catalyst to start work on the network team roadmap related to s28 and s30. They are the person to go to with anything needed from core Tor.
This week (planned):
* not much related to anti-censorship
cecylia (cohosh): last updated 2020-03-12
Last week:
- worked with GSoC students on proposals
- debugged and pushed a fix for GetTor to always send a response email (#33543)
- drafted a revision for GetTor message body (#23226)
- made a tbb patch for #33330 (#33578)
- made a patch to upgrade the version of pion-webrtc in tor browser (#33576)
- merged gitlab provider fix for gettor (#33034)
- added an update on obfs4 reachability tests (#31701)
- merged and deployed fix for ignoring quoted messages in gettor (#23225)
- started looking at update notification for proxy-go instances (#32677), i think #19409 is the way to go though
This week:
- maybe continue work on throughput check (#32938)
- make a Snowflake package for debian (#19409)
- Aggregate and write up a report of snowflake throughput changes (#32545)
- Revise GetTor help message (#23226)
- look at options for getting STUN information to snowflake clients (#25591)
- see if there's anything else we need to do for nsf ttp grant
Needs help with:
- review of tor browser patches #33578 and #33576 (tb-team)
- should we continue obfs4 reachability tests (this might be taken over by sponsor 30 work)
- any thoughts on snowflake versioning (#33593)? (required for debian packaging)
arlolra: 2020-03-12
Last week:
-
Next week:
- maybe the proxy parts of #19026
- pick another task? (#31201, #33112, #33365, ?)
Help with:
-
dcf: 2020-03-12
Last week:
- reviewed go.mod for snowflake (#33330)
- started reviewing snowflake throughput tests (#32928)
Next week:
- finish reviewing snowflake throughput tests (#32938)
- work on a fix for multiple SOCKS connections (#33519)
- maybe make new packages with 9.5a7
Help with:
cjb: 2019-03-12
Last week:
- split out #31011 into just the client-side change
Next week:
- hoping to find time to poke at golang snowflake proxy Android app
Help with:
agix:2020-03-12
Last week:
- Still on #31426
- Submitted patch for #31528
- Got familiar with HYPHAE and Salmon
Next week:
- Continue on #31426
- Work on the GSoC proposal for Salmon
Help with:
-
catalyst: 2020-03-12 (offline for this meeting)
next week:
- look at s28/s30 tickets i can help with (coordinating with ahf)
thymbahutymba: 2020-03-12
Last week:
- docker-compose for obfs4-bridge (#31834)
- multiarch docker obfs4 images #33461 (even though is more then a week ago)
- reported issue concerning #31834 (comment 25)
Next week:
Help with:
https://tails.boum.org/news/report_2020_02/
Releases
========
* Tails 4.3 was released on February 11. (bugfix release)
* Tails 4.4 is scheduled for March 12.
The following changes were introduced in Tails 4.3:
- We included the `trezor` package, which provides a command line tool
to use a Trezor hardware wallet for cryptocurrencies.
- Fix the progress bar and prevent closing the window while an upgrade
is being applied. (#16603)
Code
====
- We made great progress on Secure boot support (#6560)
and are now quite confident we can ship this in Tails 4.5 (April 7).
Thanks to everyone who answered our call for testing!
- In order to make the development process a bit smoother, we improved
the performance of our builds (#17439, #17386).
- We kept working on replacing Sikuli in our test suite (#15460), which
will allow running it on recent Debian systems. We're almost there! :)
Hot topics on our help desk
===========================
1. Users are still complaining about Seahorse failing to import public
keys. (#17183)
1. Several users reported that Stefano Zacchiroli's public key being
expired since 2020-02-07 broke our documentation about using the
command line and GnuPG to install Tails. (#17475)
https://tails.boum.org/install/expert/usb/
1. And people are still reporting GDM errors with Intel HD 630 (while
their issue is usually with their NVidia Maxwell discreet GPU)
(#16875)
Infrastructure
==============
- We've been working towards making our CI feedback loop shorter
(#16960, #17439).
- We organized the sysadmin work we will need to do as part
of migrating to GitLab.
Funding
=======
- We worked on the full proposal for the joint grant proposal with
Tor and the Guardian Project to the DRL Internet Freedom program.
- We started working on a grant proposal to the Prototype Fund.
Jobs
====
- Privacy loving Linux generalist:
https://tails.boum.org/jobs/Linux_generalist/
On-going discussions
====================
- Reconsider the terminology around "persistence":
https://lists.autistici.org/message/20200227.123500.9aee624d.en.html
Press and testimonials
======================
- 2020-02-26: Tails : le logiciel qui a permis à Snowden d’échapper aux
services secrets by Tibor Van Cutsem in Solidaire:
https://www.solidaire.org/articles/tails-le-logiciel-qui-permis-snowden-d-e…
Translations
============
## All the website
- de: 34% (2176) strings translated, 10% strings fuzzy
- es: 53% (3373) strings translated, 2% strings fuzzy
- fa: 27% (1714) strings translated, 10% strings fuzzy
- fr: 90% (5671) strings translated, 0% strings fuzzy
- it: 30% (1948) strings translated, 7% strings fuzzy
- pt: 22% (1432) strings translated, 8% strings fuzzy
## Core pages of the website
- de: 65% (1168) strings translated, 15% strings fuzzy
- es: 94% (1691) strings translated, 1% strings fuzzy
- fa: 34% (615) strings translated, 14% strings fuzzy
- fr: 98% (1755) strings translated, 0% strings fuzzy
- it: 64% (1147) strings translated, 15% strings fuzzy
- pt: 45% (820) strings translated, 14% strings fuzzy
Metrics
=======
* Tails has been started more than 808 936 times this month. This makes
27 894 boots a day on average.
[[How do we know this?|support/faq#boot_statistics]]
Hello Tor,
We started February in the rainy Berlin. We met Firefox's folks at their
bi-annual All Hands gathering and we discussed regular topics around our
collaboration. After that, many of us met at FOSDEM. We specially
enjoyed the talk diogosergio gave at the Open Design Track. You may want
to watch it!
https://fosdem.org/2020/schedule/event/git_workflow_for_design_in_os_projec…
S27 Onion services
==================
We spent February on implementing an approach to move forward with the
onion names' problem. We found that organically, developers have been
approaching this problem in different ways, mostly with solutions
tailored for the pleasure of their own service. Given that there is not
a complete solution that works perfectly for all our user groups, we
also approached this problem with a broad angle. From headers to
centralized lists we are trying to allow end-users to have an experience
close to the defaults without losing security: type a memorable domain
at the URL bar and reach an onionsite, anonymously.
As we update the URL bar to show the alias, the circuit display will
allow users to check the origin onion address for integrity. Impressive
work, acat!
You can read more about this process here
https://trac.torproject.org/projects/tor/ticket/28005
OTF Usability Lab: Tor Metrics
==============================
Last year we applied with Simply Secure for an OTF Usability Labs grant
for working on the next iteration of the metrics portal. The proposal
went through,and Nina Vizz will lead this project. Gaba and I as well
Metrics Team folks, we will be the stakeholders of this project.
User Research
=============
Nah and Piliattended the Open Design meetup, theusability testing
workshop before FOSDEM. They built together a "Download Page" research
that S9 partners will be running in March along with trainings.
We made progress on setting a workflow in git for our upcoming user
research.
https://dip.torproject.org/torproject/ux/research/issues/1
We worked on the Onion Services Research, we expect to run it virtually
and in person.
https://dip.torproject.org/torproject/ux/research/issues/3
Since we may need to localize some of this materials, emmapeel suggested
to have it in .md format. We will be working on it during March.
https://dip.torproject.org/torproject/ux/research/issues/2
WWW
===
We finally iterated torproject.org/download. We included a label for
each operative system, we improved the discoverability of the signature
files and we also made it look better in small screens.
https://dip.torproject.org/torproject/web/tpo/issues/59https://dip.torproject.org/torproject/web/tpo/issues/6https://trac.torproject.org/projects/tor/ticket/32460
S30
===
During February, ICFP fellowship Babatunde has been traveling through
Nigeria and Cameroon interviewing users who have been experiencing
information controls. He is now digesting all this material and we will
work together on expanding Tor personas in order to inform our work on s30.
L10n
====
We have updated more websites with new contentstill, no new languages
added but soon we will.
Also, we helped Snowflake and Tor Browser teams with the translations
and reviewsof the next features release.
We got some more reviewers but still, more is needed. If you are
interested in being a reviewer of a language just ping emmapeel on irc!
Fundraising
===========
Emmapeel and alsmith helped draft the MOSS proposal for the Linguine
project, to prepare an open platform for translation.
We submited a joint DRL proposal for continuing our work on user
research with communities with Guardian Project and Tails. Thanks Al and
Pili for working on this narrative and estimations!
Open Team
=========
If you missed those, February weekly meetings notes are here:
https://lists.torproject.org/pipermail/ux/2020-February/000487.htmlhttps://lists.torproject.org/pipermail/ux/2020-February/000488.htmlhttps://lists.torproject.org/pipermail/ux/2020-February/000490.html
Peace and love,
A
--
Antonela Debiasi
UX Team Lead
@antonela
E2330A6D1EB5A0C8
https://torproject.org