- tor-project - lists.torproject.org

Anti-censorship meeting notes, 07 May 2020
by Philipp Winter 07 May '20

07 May '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-07-17.58.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday May 7th 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 meeting 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 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep ------------------------- --- May 7th 2020 -- ------------------------- == Announcements == * We have a GSoC student, Hashik, who is joining the team starting this week and working on building a Snowflake proxy app for Android == Discussion == * Shall we move our anti-censorship meeting time to 17:00 or 16:00 UTC? * Will make it easier to attend for folks in Asia * What works or doesn't work for you? * Any beginning circumvention developers want experience implementing a pluggable transport? David posted a roadmap for a DNS transport. * https://lists.torproject.org/pipermail/anti-censorship-team/2020-May/000089… == Actions == * == Interesting links == * https://jewlscholar.mtsu.edu/bitstream/handle/mtsu/6199/Sheffey_mtsu_0170N_… * MSc thesis on "Adversarially Enhanced Traffic Obfuscation" * By the author of "Improving Meek With Adversarial Techniques" from FOCI 2019, https://censorbib.nymity.ch/#Sheffey2019a * https://github.com/net4people/bbs/issues/13 == Reading group == * We will discuss "Salmon: Robust Proxy Distribution for Censorship Circumvention" on May 14 * https://censorbib.nymity.ch/#Douglas2016a * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? == 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. phw: This week (2020-05-07): * Read Salmon paper. * Reviewed #34061, #34062, and #34089. * Wrapped up #30794 (lightweight censorship analyser) for now because it's working and usable so far. * More work on wolpertinger. * Filed #34089 to expose bridges.torproject.org/wolpertinger/ * Filed #34116 to look into setting up OONI's MetaDB on polyanthum (to get OONI's test results) * Wrote code to read cached-extrainfo docs and bridges stored in SQLite DB. * Some coordination with Sina regarding meek-azure. * Things are not looking good; currently no funding in sight. * A little bit of GSoC coordination. * Improved BridgeDB's email autoresponder test in #12802. * Looked into #33945 to figure out why BridgeDB's email autoresponder fails after a while. * Still not sure. Will deploy work-in-progress fixes, which may help. * Attended onionperf call. Will probably be working one day per week on it. Next week: * Help with: * https://trac.torproject.org/projects/tor/ticket/12802 Gaba: () Last week (2020-03-30): * not much related to anti-censorship This week (planned): * anti-censorship retrospective cecylia (cohosh): last updated 2020-05-07 Last week: Last week: - android reproducible build for snowflake (#28672) - GetTor twitter responder fixes (#27330) - Reproduced chrome proxy hang (#31278) - Discussed transifex issues with snowflake - snowflake webextension reviews - Investigated running a STUN server at the broker (#25591) - Created a ticket for using RFC5780 to determine the NAT type of peers (#34129) - Made PI meeting slides for next week - Onboarding Hashik (our new GSoC student) - fix for chrome idle proxy hang (#31278) This week: - sponsor 28 PI meeting (Monday, Tuesday) - More work on reviving the twitter responder in GetTor (#33036, #27330) - look at old GetTor mirrors (#33893) - More work on NAT type discovery (#34129) - Take a look at the multiplexing design for Snowflake (#25723) - investigate #33669 - Follow up on discussions of debian obfs4proxy package Needs help with: - review of GetTor twitter fixes (#27330) - review of chrome idle proxy hang fix (#31278) juggy : Temporary hiatus due to finals prep This week: - Researched XUL and dug into previous conversations around integrating Tor Launcher into Tor Browser, why porting to Web Extensions might not work, etc. Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB Help with: - arlolra: 2020-05-07 Last week: - webext repo versioning / publishing #34140, #34126, #34132, #34127 Next week: - follow ups to #33365 - start on #31201 Help with: - dcf: 2020-05-07 Last week: - merged patch to reduce Snowflake client connection timeout (#34042) - converted snowflake turbotunnel merge (#34043) into a Tor Browser ticket Next week: - review fix for Chrome proxy hang (#31278) - check with Kyle about snowflake fingerprinting results - share access to the snowflake broker CDN configuration (#30510) Help with: agix:2020-05-07 Last week: - Incoperated some more feedback on #33835 Next week: - Started work on #27984 Help with: - catalyst: 2020-04-16 last week: - more work on #5304 (PT outbound bind address) - started looking at #29128 (assemble bridge line) this week: - more background research and work on s28/s30 tickets thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with:

1 0

S58 Meeting on Mondays at 1800 UTC [Tor Browser Security, Performance, & Usability Improvements]
by Gaba 05 May '20

05 May '20

Hi! We are meeting every Monday at 18:00UTC to coordinate the project S58's work [0]. Next meeting is on May 11th. Agenda and notes: https://pad.riseup.net/p/_kbebKhZvNcUuqxQL5NV cheers, gaba [0] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor58 -- she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Network health meeting notes, 4 May 2020
by Georg Koppen 05 May '20

05 May '20

Hi! We just had a short sync yesterday about network health work. You can find the IRC log at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-05-04-17.59.log… There was no pad involved this time, so no notes from it. Moreover, this was the last network-health meeting for quite some time I suspect as we are currently reorganizing our team structure in the wake of the recent lay-offs. There is no network-health team anymore and network-health topics will likely be part of meetings concerned with core Tor work in the foreseeable future. But details are not set yet. Georg

1 0

Do you own the dockerhub user name torproject?
by Philipp Winter 04 May '20

04 May '20

I recently tried to set up an organisational dockerhub account named torproject but the name was already taken, by a seemingly inactive user account: <https://hub.docker.com/u/torproject> Does anyone on here own this account, or knows who might? Thanks, Philipp

1 0

Anti-censorship team monthly report: April 2020
by Philipp Winter 01 May '20

01 May '20

Hi all, Here's what the anti-censorship team has been up to in April: Snowflake --------- * Merged Turbo Tunnel features into Snowflake. (Allows persisting a session across separate proxies.) <https://bugs.torproject.org/33745> <https://lists.torproject.org/pipermail/tor-talk/2020-April/045571.html> Merging into Tor Browser is pending: <https://bugs.torproject.org/34043> * Implemented measures to hand out more restrictive proxies less often. <https://bugs.torproject.org/33666> * Split Snowflake into two repositories(one for Go, one for the web-based proxy code). <https://bugs.torproject.org/33593> * Updated pion webrtc in Tor Browser. <https://bugs.torproject.org/33576> BridgeDB -------- * Moved forward with creating a feedback loop between OONI and BridgeDB. Work-in-progress code is available at: <https://gitlab.torproject.org/torproject/anti-censorship/wolpertinger> <https://bugs.torproject.org/32740> * Removed PGP support from BridgeDB. The feature has been broken for quite a while, is overly complex, and not particularly useful. <https://bugs.torproject.org/17548> * Renamed a bunch of source code files in BridgeDB, so they no longer collide on a file system that's case insensitive. <https://bugs.torproject.org/29686> * Made BridgeDB's email responder more usable. The instructions are now more clear and it will return with bridges no matter what -- even if the user's request was malformed. <https://bugs.torproject.org/30941> * Improved a Python script that tests BridgeDB's email responder by periodically sending email. <https://bugs.torproject.org/12802> * Made progress towards improving the robustness of BridgeDB's email autoresponder, so it no longer gets confused by Gmail's quoted-printable responses. <https://trac.torproject.org/projects/tor/ticket/33835#ticket> GetTor ------ * Fixed a bug caused by malformed email addresses. <https://bugs.torproject.org/34027> * Refactored to remove duplicate code. <https://bugs.torproject.org/34035> * Cleaned up logs. <https://bugs.torproject.org/34061> * Fixed a bug in the service shutdown code. <https://bugs.torproject.org/34062> * Removed a bunch of old GetTor code. <https://bugs.torproject.org/32912> Miscellaneous ------------- * Reviewed a submission for the Tor Research Safety Board. * Moved forward with creating a "censorship snapshot" that encodes how each country blocks Tor. Eventually, this snapshot should help Tor Browser figure out how to best circumvent in each country. <https://bugs.torproject.org/28531> * Built a prototype of a lightweight censorship analyser that's meant to be run by censored users. It can help us create the censorship snapshot in #28531. <https://bugs.torproject.org/30794> * Created a new mailing list for anti-censorship service outage alerts. If this interests you, you can subscribe here: <https://lists.torproject.org/cgi-bin/mailman/listinfo/anti-censorship-alerts> * We organised two reading groups, in which we discussed the following two papers: <https://censorbib.nymity.ch/#Wang2020a> <https://censorbib.nymity.ch/#Nasr2020a> Cheers, Philipp

1 0

Anti-censorship meeting notes, 30 Apr 2020
by Philipp Winter 30 Apr '20

30 Apr '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-04-30-17.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday April 30th 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 meeting 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 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep ------------------------- --- April 30th 2020 -- ------------------------- == Announcements == * We created anti-censorship-alerts(a)lists.tp.o for service outage alerts. * Feel free to subscribe. * https://lists.torproject.org/cgi-bin/mailman/listinfo/anti-censorship-alerts * Alerts for * gman999's sysmon instance * prometheus instance * nagions instances * gettor's email autoresponder * bridgedb's email autoresponder * Also, send email there if any of our services are broken. == Discussion == * We should monitor indicators that tell us if we're on the right track * # of bridge users * # of bridge users from bridges that were privately distributed * # of bridges/snowflakes * volume of traffic on snowflake / meek bridges * snowflake https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6… * meek https://metrics.torproject.org/rs.html#details/8F4541EEE3F2306B7B9FEF1795EC… * Make it easier for people to report bugs -> gives us an idea of what users are struggling with * Blog more and hear from users in comments * Read frontdesk emails & get a sense of the variety of questions and how many get resolved * Track a project's "activity" by keeping track of its commits * Check what other people are tracking, in different contexts, and see if we can apply their indicators * Track # of user-reported tickets * Number of countries where vanilla Tor Browser works / doesn't work, where Tor Browser + default bridges work/doesn't work, and + obfs4. == Actions == * Please add your April 2020 work highlights to our monthly team report: * https://pad.riseup.net/p/CANAMyvGfb-wtKfzN2R_ == Interesting links == * https://ssd.eff.org/en/module/understanding-and-circumventing-network-censo… * Surveillance Self-Defense: Understanding and Circumventing Network Censorship * https://protonmail.com/blog/anti-censorship-alternative-routing/ * Protonmail will introduce a new "alternative routing" feature. * No technical details. May be domain fronting. == Reading group == * We will discuss "MassBrowser: Unblocking the Censored Web for the Masses, by the Masses" on April 30 * https://censorbib.nymity.ch/#Nasr2020a * https://massbrowser.cs.umass.edu/ * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? == 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. phw: This week (2020-04-30): * Emailed a bunch of people to get an idea of meek-azure's financial situation. * Offboarding activities. * Addressed feedback for our lightweight censorship analyser (#30794). * Asked for new mailing list for anti-censorship service alerts. * Asked for Nagios alerts to be sent there (#34028). * Reviewed #33666, #33835, and #34035. * Continued work at wolpertinger. Added code to read serge's extrainfo descriptors. * Started taking a look at ICLab's measurements of our default bridges. * More talking to sysadmins to finally move our monitoring forward. Next week: * Help with: * #30794 Gaba: () Last week (2020-03-30): * not much related to anti-censorship This week (planned): * anti-censorship retrospective cecylia (cohosh): last updated 2020-04-30 Last week: - so many reviews - refactored some GetTor code (#34035) - rebased pion-webrtc update patch in tbb (#33576) - looked at datachannel timeout in client (#34042) - squished some new snowflake bugs (#34049) - update node wrtc package (#34053) - updated snowbox to work with new repo setups - updated snowflake web proxy - started building snowflake for android (#28672) - squashed some GetTor bugs (#34061, #34062, #34027) - kept up with sponsor 28 evaluation phase This week: - test snowflake for android on mobile device - set up some kind of NAT topology testing suite (#25595) - figure out what we need to do to revive the twitter responder in GetTor (#33036) - look at old GetTor mirrors (#33893) - investigate #33669 - clean out and update any old tickets lying around - help with sponsor 28 PI meeting slides Needs help with: - review of GetTor fixes (#34061, #34062) juggy : Temporary hiatus due to finals prep This week: - Researched XUL and dug into previous conversations around integrating Tor Launcher into Tor Browser, why porting to Web Extensions might not work, etc. Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB Help with: - arlolra: 2020-04-30 Last week: - some sporadic review Next week: - follow ups to #33365 - start on #31201 Help with: - follow up review of #33365 dcf: 2020-04-30 Last week: - merged snowflake turbotunnel branch and redeployed bridge (#33745, thanks arma and cohosh) - removed client-side buffering from snowflake, and related refactorings (#33897, #33982, #33984, #33994, #33995, #33996, #33997, #34002, #34049, #34050, thanks cohosh and arlolra) - filed a ticket to reduce snowflake client connection timeout (#34042) - made a branch for updating to turbotunnel snowflake in Tor Browser (#34043) Next week: - patch to reduce connection timeout (#34042) - convert snowflake turbotunnel merge (#34043) into a Tor Browser ticket - check with Kyle about snowflake fingerprinting results - share access to the snowflake broker CDN configuration (#30510) Help with: cjb: 2020-04-30 Last week: - gonna be afk with kids Next week: Help with: agix:2020-04-30 Last week: - Incoperated phw's feedback on #33835 and #31528 Next week: - finalize #33835 and #31528 - Pick up a new ticket Help with: - catalyst: 2020-04-16 last week: - more work on #5304 (PT outbound bind address) - started looking at #29128 (assemble bridge line) this week: - more background research and work on s28/s30 tickets thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with:

1 0

Community Council activity summary, October 2019 - March 2020
by Taylor Yu 30 Apr '20

30 Apr '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, Here is a brief summary of the Community Council's activities from October 2019 through March 2020. March 2020 The Council participated in the membership audit process. February 2020 The Council talked with some people from the relay operator community about extending the code of conduct for relay operation. It probably makes more sense to make a separate guidelines document about ethical relay operation. January 2020 The Council started a dialog with grants and communications teams about making sure the potential donors and guest bloggers are aligned with our community values. December 2019 no significant actions November 2019 The Council reviewed an existing community health concern. October 2019 The Council received an email containing suggestions for revising the Code of Conduct. One immediately actionable suggestion was to fix an incorrect email address for the Community Council. An appropriate email alias was created to work around the problem. - --- end of summary --- This summary will also be posted on the Council's wiki page. If you have any feedback about this summary format, or any other feedback to the Council, please contact us at tor-community-council(a)lists.torproject.org. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBCAAGBQJeqjBDAAoJEKMvF/0AVcMFQoML/iKK2UbDWpbBQjweas22EROF MDSIgoBD35ywGV7qlWUNO/sZCFhgs/c4HSsmC2xCvUD1FjF/J9YBDzIHmCX6Ew4o TkK39/yAo3P+IbRFDxcNcEPaGT/8MqlpMUC6lvic5CmygLxRJeBi49j4bdXcI1to 7M0Omi2cbK7RFUQCxk6VrmSuE+C/NwUbEZPzCRQgzDXPFtoecIip6EtbupciDFFz ePRItO6mlyqpBoqex+f5TrxDfhuvmqGpD4ld93azsWWO2dFK9M8pMt+cNnxA/lMl KCoIzVO/Cy/jcQ8IkRz+TeVROQrJtpxjRCVoS55bDJYhtT3sGgLGjv0QK8N0xx9Q RC4k3rFOEpUmYaVALChSL5isxIS86m+paxvHBH5avCqBWD2vYz3UiFgNZRHzRJut DkmTQNgJzKzfpmm9KER9yleNDvb4OeboTficC6pVipAr4xmY4mgXmbrqduO75gEi m+Eo02YD+qVWJKqh0mKyDbqDd6VXYKyodfJqqwGVXA== =hYTD -----END PGP SIGNATURE-----

1 0

February Fundraising Report
by Sarah Stevenson 29 Apr '20

29 Apr '20

Below you will find the Fundraising Team's February report. Please let us know if you have any questions! ## Grants DRL: We have been working on submitting two full proposals to DRL, one for usability (joint project with Tails & Guardian Project) and another for scalability. We will submit these at the beginning of March. Zcash Foundation: Zcash Foundation granted us $50,000 to work on the Specification phase of the Walking Onions proposal[1]. Thank you Chelsea for making this connection, and to Nick for helping to write the proposal and advocate for the work. We still need funding for the proof-of-concept and implementation phases of Walking Onions. If you know someone, or some entity, that might be interested in supporting this work, please let us know! Nathan Cummings Foundation: A joint proposal with FPF we submitted was declined. DIAL Open Source Center: We submitted a small proposal to DIAL to help support the Walking Onions work. OTF: We are working on a third round of OTF revisions on the Tor Browser proposal. We submitted a Learning Lab application to help publicize the onion services work in Sponsor 30. OTF also agreed to fund an in-person meeting to do some work on DDoS protections as it pertains to high profile onion services. We submitted some informal requests to the Judith Neilson Institute for Journalism & Ideas and the Omidyar Foundation. We also met with the Internet Society Foundation. ## Donate Buttons on Website We closely monitor organic donations made via donate.torproject.org. By ‘organic’ we mean non-monthly donations generated primarily via donate links throughout our webpages. It is important to track this income because it accounted for $231,472 in FY18, $239,479 in FY19, and $334,418 so far in FY20. Small changes to our web pages can affect this income. This graph[2] shows average daily online income per month. This clearly illustrates the importance of our EOY campaign and the call to action on about:tor. There are a few other events to note in the past year. The new website launched in March 2019. The first iteration did not include a prominent donate button and the average daily income decreased until we made the donate button yellow April 26th. Then average daily income increased modestly, and increased significantly after May 26th when we added the donate link to about:tor. Since that addition, we have been averaging $600 per day in organic donations (except during the campaign when the average was significantly more.) At the end of February 2020, we saw a sharp decline in these organic donations. We suspected the redesign of /download was partially responsible. Antonela quickly added the yellow donate button back to that page and we saw donations go back up to about where they were in early February. This prompted us to take a look at other modifications and we decided to highlight the donate language on /thank-you and the donate language on about:tor will be updated upon the next release. We are also beginning plans to update donate.torproject.org and are working with Giant Rabbit to be able to make those changes ourselves. ## Events We are still planning for the major donor event in San Francisco March 26th and foundation lunch in New York April 13th. Hopefully covid-19 will not alter those plans. ## Newsletter/Email list We are still seeing around 10,000 people join our email list each month and now have over 179,000 subscribers. Since the list was so large, it was taking around 24 hours to send an email message to the whole group. Giant Rabbit made some changes to our system and now a bulk email is delivered in around 3 hours. Each new subscriber gets a welcome email a day or two after they join the list and then are offered a sticker pack for a $17 donation a few weeks after that. [1] https://grants.zfnd.org/proposals/1642205075-walking-onions-scaling-the-tor… <https://grants.zfnd.org/proposals/1642205075-walking-onions-scaling-the-tor…> [2] https://trac.torproject.org/projects/tor/attachment/wiki/org/teams/Fundrais… <https://trac.torproject.org/projects/tor/attachment/wiki/org/teams/Fundrais…> Sarah Stevenson (she/her) Fundraising Director The Tor Project sstevenson(a)torproject.org Take back the internet with Tor. https://donate.torproject.org/ Public Key: 93B3 AC08 4257 FA3D D4BB 8E95 CC08 5DBA C015 612A

2 2

Anti-censorship meeting notes, 23 Apr 2020
by Philipp Winter 23 Apr '20

23 Apr '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-04-23-17.58.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday April 23th 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 meeting 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 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep ------------------------- --- April 23th 2020 -- ------------------------- == Announcements == * We've now officially split snowflake into two repositories * Go implementation: gitweb.torproject.org/pluggable-transports/snowflake.git/ * Web-based proxy code: gitweb.torproject.org/pluggable-transports/snowflake-webext.git/ * Kyle, the researcher who is investigating Snowflake's network fingerprint, has found differences in Snowflake's DTLS handshake (different offered extensions) relative to Facebook Messenger, Hangouts, and Discord. He is planning to file a ticket with details. == Discussion == * == Actions == * == Interesting links == * == Reading group == * We will discuss "MassBrowser: Unblocking the Censored Web for the Masses, by the Masses" on April 30 * https://censorbib.nymity.ch/#Nasr2020a * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out, in hopes that others will pick it up? == 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. phw: This week (2020-04-23): * Offboarding meeting for Tor's exit scanner. * Spent a bit of time looking into porting exitmap to Python 3. * Reviewed #32912, #33835, and #31528. * More improvements to script that tests BridgeDB's email autoresponder (#12802). * Some organisational tasks (TTP grant, DARPA PI meeting). * Asked around wrt status of meek-azure. * Moved forward with "censorship snapshot" (#28531). * In the process, improved our lightweight censorship analyser, which can help with that (#30794). * More thinking about feedback loop between BridgeDB and OONI. * There are similarities to Salmon: we may want to implement a simplified Salmon for this task. Next week: * Help with: * #28531 Gaba: () Last week (2020-03-30): * not much related to anti-censorship This week (planned): * anti-censorship retrospective cecylia (cohosh): last updated 2020-04-23 Last week: - lots of meetings - discussed #28325 and #33953 with GeKo and boklm - revised solution to snowflake proxy failures (#33666) - revised and merged PRs to separate snowflake repos (#33593) - merged cleanup of gettor scripts (#32912) - popets things - sponsor 28 evaluation work - started looking at GetTor twitter responder and telegram bot work (#33036, #22011) This week: - get a tor browser android build running - start working on snowflake for android (#28672) - set up some kind of NAT topology testing suite (#25595) - look into setting up a TURN server (#25596) - figure out what we need to do to revive the twitter responder in GetTor (#33036) - look at old GetTor mirrors (#33893) Needs help with: - review of snowflake proxy failure solution (#33666) juggy : This week: - Researched XUL and dug into previous conversations around integrating Tor Launcher into Tor Browser, why porting to Web Extensions might not work, etc. Next week: - Implement audio captchas in moat, figure out how to reduce audio captcha request size - Keep studying BridgeDB Help with: - arlolra: 2020-04-16 Last week: - start on #33365 - review of #33593 Next week: - follow ups to #33365 - review of #33666 - start on #31201 Help with: - review of #33365 dcf: 2020-04-23 Last week: - reviewed Go 1.13 upgrade (#32027) - commented on design for self-limiting failing proxies (#33666) Next week: - respond to feedback on turbotunnel merge branch (#33745) - branch for snowflake turbotunnel merge into Tor Browser - share access to the snowflake broker CDN configuration (#30510) Help with: cjb: 2020-04-23 Last week: - gonna be afk with kids Next week: Help with: agix:2020-04-23 Last week: - Kept working on #33835 Next week: - finalize #33835 - finalize #31528 Help with: - catalyst: 2020-04-16 last week: - more work on #5304 (PT outbound bind address) - started looking at #29128 (assemble bridge line) this week: - more background research and work on s28/s30 tickets thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with:

1 0

update on team meetings this week
by isabela 20 Apr '20

20 Apr '20

Hi there, Here is an update regarding team meetings this coming week, as you can see must teams wont be having their weekly meetings this week. We will send another update at the end of the week regarding when meetings will be resumed. Teams that will not have meeting: Metrics Network Community Network Health Browser www (contact: hiro) UX Teams that will have meeting: anti-censorship Please email teams at their email lists if you have any specific questions for them. thank you, isabela -- Isabela Bagueros Executive Director The Tor Project https://www.torproject.org http://expyuzz4wqqyqhjn.onion/

1 0