- tor-project - lists.torproject.org

Network Team Meeting Notes, 10 February 2020
by Alexander Færøy 19 Feb '20

19 Feb '20

Hello, Here is a short summary of the network team meeting from Monday the 10th of February 2020. 1) We started out with roadmap. People are doing 0.4.3 tickets and TROVE's. 2) Reviews seemed alright. 3) We went over our 0.4.3 status page. 4) Short discussion on reviewer assignments. 5) Nick asked if we had any blockers for a 0.4.3.2-alpha release. Nobody had any. 6) 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-02-10-17.59.html Below are the contents of our meeting pad: Nick: Week of 2 Feb (planned): - Finish bug retrospective. - Solve as many 043-must/should issues as I can. - Review and merge. - Keep an eye on blog comments about recent stable releases. - Plan for an alpha early next week. - More work on paper with Ian and Chelsea (revisions due 15 Feb) - Review Teor's proposal 313 once it's out - Integrate revisions to prop295 before I forget completely Week of 2 Feb (actual): - Continue bug retrospective - Worked on paper with Ian and Chelsea - Revised C style branch (32921) - Worked on several 0.4.3.x tickets - Discussed and worked on several TROVE issues. - Spent Friday sick :/ Week of 10 Feb (planned): - Work on paper with Ian and Chelsea (revisions due 15 Feb) - Finish review on PETS artifact (due 15 Feb) - Review Teor's proposal 313 - Revise: - TROVE-2020-002 - 33104 -- SIGNAL ACTIVE patch - 32921 -- C style branch - Other patches on 0.4.3 - Release 0.4.3.2-alpha - Continue bug retrospective. Finish? - Open merge window for 0.4.4 - Resolve more 043-must/should tickets - Integrate revisions to prop295 before I forget completely Pending for later: - Try to do a personal roadmap for next 3-4 months catalyst: week of 02/03 (2020-W06) (planned): - reviews - getting feedback on .github repo stuff (#32335) - feedback cycle stuff week of 02/03 (2020-W06) (actual): - more review of gsod work (#32928, #32929), with nickm's help - research on "minimum viable clang-format version" for #32921 week of 02/10 (2020-W07) (planned): - reviews - more research and commenting on #32921 - follow up on .github repo stuff (#32335) ahf: Week of 3/2 2020 (planned): - Work on one of the TROVE's. - Tried to wrap my head around the HS randevouz blog post. - EOM tasks from January. - Some follow ups related to peer review and FOSDEM. Week of 3/2 2020 (actually): - Did EOM tasks for January. - A lot of follow ups from meetings. - Wrapped my head more around sbws. - Started working on my TROVE issue. - Made a notebook on "churn rate" after Roger talked about on IRC: https://github.com/ahf/onion-notebooks/blob/master/relay_churn_rate.ipynb - some of this surprised me. Week of 10/2 2020 (planned) - Get over a flu. Going in the right direction. - Review a lot of sbws tickets. - Finish TROVE issue. - Work on wiki migration on GL. Help hiro with migration if she needs that. - Write email about a discussion I had with Peter Stuge and Linus at FOSDEM. asn: Week of 03/01 (actual): - Asked people to pre-alpha test OBv3: https://github.com/asn-d6/onionbalance/blob/master/docs/alpha-testing-v3.txt - Handled various security threads and also started handling TROVE-2020-003 - Recovered from FOSDEM and handled all the backlog Week of 10/01 (planned): - Finalize handling of TROVE-2020-003 - Get back to onionbalance v3. - Get #32709 merged - Finish reviews Mike (reporting on tor-project@lists unless active on tor.git): Last week (planned): Last week (actual): This week (planned): - Funding proposals - May work on vanguards+onionbalance integration tests dgoulet: Week of Feb 3rd (actual): - Reviews and merges - HS client auth issues. Worked on fixes: #33139, #33148 - Worked on #28992 HS ticket. - More work on #33072 and #33029. Launched a discussion on the dirauth list to decide for backport on those. - Sponsor27 meeting. Wrote a summary of the new SOCKS5 extended error in #33035. - Some work on the network health side to help GeKo transition. - Went over the TROVE and responded on network team security list. - HackerOne report. Week of Feb 10th (planned): - Backport work for #33072 and #33029. - Update #32910 with latest discussion with nickm about the tracing API and code structure. - Will start doing some slides for NetDev 0x14. Diagrams of some tor low level internal codes are needed so I need to start early. Gaba: Week of February 6th (actual) - 255 - run behind Trac - sbws roadmap Week of February 10th (planned) - s55 - reduce scalabiltiy project to fit new requirements - sbws proposal - survive a pile of mails - run behind trac again - read some Tor documents teor: (online first meeting of the month, offline at the usual meeting time) Week of 3 February (planned): Take Time for: - Revise Proposal 311: Relay IPv6 Reachability (#24404) - Revise Proposal 312: Automatic Relay IPv6 Addresses (#33073) - Draft Proposal 313: Relay IPv6 Statistics (ticket?) - sbws roadmap review - sbws funding proposal review - Merge proposals 311 and 312, and send out final drafts to tor-dev Roadmap: - Make tickets for roadmap, based on proposals 311 and 312 Other: - Ticket triage, backport deciding, quick code reviews Week of 3 February (actual): Take Time for: - Revise Proposal 311: Relay IPv6 Reachability (#24404) - Revise Proposal 312: Automatic Relay IPv6 Addresses (#33073) - Merge proposals 311 and 312 - Start Drafting Proposal 313: Relay IPv6 Statistics (#33159) - sbws roadmap review - responding to emails and IRC Roadmap: - responding to questions on sponsor 55 tickets - update other tickets based on Sponsor 55 analysis and proposals Other: - Ticket triage, backport deciding, quick code reviews - Opened #33156 for a DoS subsystem IPv6 bug - GSoC potential IPv6 project: update project info based on latest proposals - Security issue analysis - Python 3 reviews / helping new contributors Week of 10 February (planned): Take Time for: - Write Draft of Proposal 313: Relay IPv6 Statistics (#33159) - Revise Proposal 313 based on reviews - responding to emails and IRC Roadmap: - open Sponsor 55 tickets for required work - based on proposals - with updated estimates - make existing tickets children of Sponsor 55 parent tickets Other: - Ticket triage, backport deciding, quick code reviews - Python 3 reviews / helping new contributors Week of 10 February (actual): Take Time for: - Write Draft of Proposal 313: Relay IPv6 Statistics (#33159) - Revise Proposal 313 based on reviews - Proposal 313 based on reviews - responding to emails Roadmap: - started opening Sponsor 55 tickets for required work - based on proposals - with updated estimates - made some existing tickets children of Sponsor 55 parent tickets - found a relay bandwidth stats bug that probably affects IPv6 stats (#33201) Other: - Ticket triage, backport deciding, quick code reviews - Python 3 reviews / helping new contributors Need help with: - Please review Proposal 313: Relay IPv6 Statistics: (for Sponsor 55) https://lists.torproject.org/pipermail/tor-dev/2020-February/014158.html jnewsome: week of 02/03 (2020-W06) (planned): week of 02/03 (2020-W06) (actual): - Onboarding logistics - Fleshed out Shadow sponsor page a bit https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor38 - Fixed some Shadow compiler warnings and bugs (https://github.com/shadow/shadow/issues/711 and related issues) week of 02/10 (2020-W07) (planned): - Enable -Werror in Shadow, suppressing existing warnings if necessary (https://github.com/shadow/shadow/issues/711) - Add clang compile to CI - Fix remaining tests that listen on hard-coded ports (https://github.com/shadow/shadow/issues/718) - Start planning Shadow TCP redesign -- Alexander Færøy

1 0

Tor Browser Release meeting this week: Wednesday 19th February @ 19UTC
by Pili Guerra 18 Feb '20

18 Feb '20

Hi everyone, It’s Tor Browser Release meeting week once again! Let’s discuss our alpha release cycles and whether we have any candidate features for release next week. Thanks, Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

Network health meeting notes, 17 Feb 2020
by Georg Koppen 18 Feb '20

18 Feb '20

Hello! Yesterday, we held weekly meeting related to network health. For those of you who missed it (or just wanted to recap the meeting), the IRC log can be found on: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-17-18.59.log… Here comes what we were up to in the previous week(s) and what we plan to work on in the coming week: GeKo: Last week: - away from the keyboard This week: - more work on simplification of bad relay rejecting process (#33182) - digging out of backlog - getting up-to-speed for sbws code review/work ahf: Last week: - Tried to build up some intuition on relay churn rate and did: https://github.com/ahf/onion-notebooks/blob/master/relay_churn_rate.ipynb Gus: This week: - Send to GeKo legal questions to add to EFF Legal FAQ - Emailed a brazilian relay operator to update their outdated tor relay Gaba: Last and this week: - sbws proposal for funding - moderation on tor-relay operators mailing list Georg

1 0

Notes from Vegas Meeting FEBRUARY 17 2020
by Erin Wyatt 13 Feb '20

13 Feb '20

REMINDER: Monday, February 17 is a US Federal holiday (observed). The holiday calendar is now in NC and shared with all people/teams. Vegas Team Meeting Notes FEBRUARY 13 2020 + OLD BUSINESS anarcat: - reminder: sandstorm/bracteata decomissionned, data will be destroyed in 7 days! + NEW BUSINESS Karsten: - Found a possible alternative to MaxMind's GeoLite2 database. Mike: - I have a roles description pad; I feel like some wide conversation might be needed. Discussion: He'll send email about it. + GENERAL NOTES Karsten: 1. Discussed possible graphs for performance/scalability experiments (#33076) and the torflow/sbws transition (#33077). 2. Found a possible alternative to MaxMind's GeoLite2 database Gus 1. Launched Tor Village Call For Proposals in IFF. Please share with your friends: https://lists.torproject.org/pipermail/tor-project/2020-February/002723.html 2. Helped Nah with her fellowship application 3. Reviewing Cleo's work in Frontdesk 4. Rotationmatrix is working with relays metrics to assist new relay operators. If you have thoughts about what's a good ISP and metrics queries, please come to talk with us on channel #tor-www 5. We will have a second edition of #DocsHackathon in March. 6. Adding comments to DRL proposal 7. For the next months, we will merge Global South IRC meetings with our regular Community Team meetings. Philipp 1. Wrote BridgeDB blog post with Steph's help. 2. Attended Sponsor 30 sync meeting and got conversation with OONI started. 3. Still lots of work on porting BridgeDB to Python 3. Close to being done now! 4. Forwarded speaking invitation for the Android Security Symposium to the Guardian Project. Mike: 1. Migrated Storm Perf R&D Pipeline to Gitlab: https://dip.torproject.org/mikeperry/scalability-and-perf-board/-/boards 2. Worked on DRL proposal 3. Thinking about how to comunicate my new role/responsibilities... Alex: 1. Hit by some post-FOSDEM flu. Catching up from this. 2. Team seems to be doing well. New IPv6 grant is taking off nicely with Teor running it. 3. Submitted talk with Geko to FOSS North. 4. Working on SBWS, 0.4.3, and a TROVE bug right now. Steph: 1. Working with OTF Learning Lab. Reviewing a narrative outline. 2. Mentoring annalee_ on tasks. She has completed fixing blog tag typos and redundancies and is working on the press list and a post on VPNs. 3. Preparing for SF events. Making edits to our material deck. anarcat 1. ordered new server for the ganeti cluster (fsn-node-04) 2. shutdown first server in a series of five to be migrated into the cluster (yaaaay!) 3. more work on install process automation (automated root alias creation #32283 , puppet bootstrap improvements, package cleanups) 4. reviewing work to deploy a new gitlab instance to fix the weird MR bugs 5. sandstorm/bracteata decomissionned, data will be destroyed in 7 days! 6. proposed TPA-RFC-1 process for offline discussions, details in https://help.torproject.org/tsa/policy/tpa-rfc-1-policy/ 7. usual weekly stuff (puppet refactoring #33277 #32914 and review, debian packaging and bugtracking, new RT queue, RT mail spam, new packages on server 8. answer questions about nextcloud/SVN, to be continued... Gaba 1. DRL proposal cutting down estimates with MikePerry 2. on getting rid of SVN 3. Metrics roadmap 4. SBWS proposal writing 5. Sponsor 55 - reading proposals 6. Sponsor 30 follow up 7. SF Event - need to send invitations this week 8. follow up on attempts to make tor size smaller - https://trac.torproject.org/projects/tor/ticket/33291 9. music track for this week https://www.youtube.com/watch?v=AuHzDFqVDs4 < nice :) Nick 1. New alpha release out, again :) 2. not much is new; aiming for alphas every couple of weeks till we're stable. 3. 0.4.4 is branched 4. Had meeting about library size; need to figure out next steps Sarah 1. Planning for San Francisco and NYC events 2. General monthly fundraising tasks 3. Got a nice $20K bitcoin gift this morning. No word who it is from yet Matt: 1. Tor Browser 9.0.5 released 2. Tor Browser 9.5a5 release in progress 3. Continuing Tor Browser roadmapping for upcoming migration 4. Trying to keep track of Sponsors 9, 27, and 30 work 5. Need to begin work on Tor embeddability library ewyatt: 1. REMINDER: Monday, February 17 is a US Federal holiday (observed). The holiday calendar is now in NC and shared with all people/teams. 2. Executive Assistant job description is published; please share! https://www.torproject.org/about/jobs/executive-assistant/

1 0

Metrics Team Meeting Notes, February 13th 2020
by Gaba 13 Feb '20

13 Feb '20

Hi! We had our weekly metrics team meeting today. The next one is going to be on February 20th at 1500 UTC. The pad for the meeting in 2020 is at https://pad.riseup.net/p/tor-metricsteam-2020.1-keep The log for the meeting is: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-13-15.01.log… And the agenda/notes: ------------------------------------- Agenda Thursday, February 13th, 15 UTC ------------------------------------- Review tasks from roadmap session (ticket creation, old cards in trello) https://pad.riseup.net/p/0K2Q5uuN0CbjbOGxJQsL-keep Karsten and Acute creates needed tickets for OnionPerf project and set them with #metrics-team-roadmap-2020Q1 Iain creates needed tickets for ExitScanner Action: Gaba set keyword #metrics-team-roadmap-2020Q1 for all tickets in the roadmap Action: Gaba updates trello kanban board with roadmap Action: Gaba will update https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor59 Check on tickets from network health 33176 33178 Proposal 313 - https://lists.torproject.org/pipermail/tor-dev/2020-February/014158.html Metric queries for GoodBadISPs https://dip.torproject.org/torproject/web/community/issues/72#note_483 Monthly reports, are they worth the effort? Let's try a quarterly report for Q1 and then monthly reports starting in April. GitLab migration and whether OnionPerf should stay or not Do everything in Trac until the transition is official. Alternative to MaxMind's GeoLite2 database (#32978) Onionoo 8.0 release and deployment preparation Metrics of Metrics / Network Health -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Anti-censorship meeting notes, 13 Feb 2020
by Philipp Winter 13 Feb '20

13 Feb '20

Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-13-17.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday February 13th 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://dip.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 * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting's notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://dip.torproject.org/groups/torproject/anti-censorship/gettor-project… * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Projects 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 ------------------------- --- February 13th 2020 -- ------------------------- == Announcements == * == Discussion == * shall we use un-reviewed yet complete translations in snowflake? see #33132 and #32035 * an update on the discussion on tor library size from meeting with TGP this week? == Actions == * == Interesting links == * == 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-02-13): * Merged #32860 (make obfs4 Docker image smaller). * Still more work on Python 3 port. Should be almost done now. Test-deployment on polyanthum will probably highlight more issues though. * Created OONI pull request to add our latest default bridge to their scan targets. * Wrote BridgeDB "what's new?" blog post with Steph's help: https://blog.torproject.org/new-release-bridgedb-093 * Attended Sponsor 30 sync meeting. * Filed #33299 (retire obfs3, scramblesuit, and fte from BridgeDB) and wrote a patch. * Closing #33007 now that our bridge campaign retrospective is done. Next week: * Hopefully finish Python 3 port * Write a summary of our current BridgeDB distribution mechanisms and brainstorm new ones Help with: * #33299 Gaba: (2020-02-13) Last week (Feb 13th): * This week (planned): * prioritize roadmap into gitlab cecylia (cohosh): last updated 2019-02-13 Last week: - reviewed #30716, #32860, #19026 - finished up fixes for gettor's rate limiting (#33123) - moved gettor's database library from twisted and wrote some tests for gettor's database functions (#33193) - have GetTor ignore quoted help message (#23225) - worked with emmapeel on updates to snowflake's translation (#33132 and #33306) - grant revisions - discussed snowflake scaling for a future grant - checked out most recent snowflake + turbotunnel changes and dogfood This week: - UI mock up for snowflake throughput check (#32938) - Aggregate and write up a report of snowflake throughput changes - work on snowflake proxy-go issues (#33211) - write up snowflake scaling thoughts for mailing list - send grant to some external reviewers - pick up another gettor ticket Needs help with: - review of #31971 (from tor browser team, in progress) - review of #33193 and #33123 (hiro) - review of #23225 (phw?) arlolra: 2020-02-13 Last week: - merged the client part of #19026 Next week: - maybe the proxy parts of #19026 - pick another task? Help with: - dcf: 2020-02-13 Last week: - did Let's Encrypt upgrade for Snowflake bridge (#32964) - made Tor Browser builds with Snowflake and Turbo Tunnel - https://lists.torproject.org/pipermail/anti-censorship-team/2020-February/0… - https://lists.torproject.org/pipermail/anti-censorship-team/2020-February/0… Next week: - open ticket to deploy the turbotunnel Snowflake bridge Help with: cjb: 2019-02-13 Last week: - not much time! Next week: - saw another request for an Android proxy app with golang snowflake code go by, am up for helping getting that going. Help with: - still waiting for review of #31011, will make it a PR on GitHub agix:2020-02-13 Last week: -Struggled with setting up Bridgedb, finally got it up running, #31967 basiclly fixed Next week: -Test #31967 fix, Fix #31876 Help with: -Is there a certain test specification I should follow for testing fixes?

1 0

Tor Village at IFF: Call for Proposals [February 13th - March 10th]
by gus 13 Feb '20

13 Feb '20

Hello, Today we are opening our Call for Proposals to the Tor Village that will take place in IFF, Valencia (Spain). Please share with your friends! :) cheers, Gus ----- Tor Village at IFF: Call for Proposals ====================================== CFP date: February 13th - March 10th Tor Village: April 23 and 24, 2020 - IFF, Valencia, Spain. During this year's Internet Freedom Festival (IFF) edition, the Tor Project will organize a Tor village with activities on privacy, anonymity, and anti-censorship based around the technology we build. IFF will take place from April 20 - 24 and the Tor Village will take place on the last two days, April 23 and 24 2020 in Valencia, Spain. The Call for Proposals for the Tor Village will be open from February 13 to March 10, 23:59 UTC. The activities will be approved by the Tor Project Community Team and the participants will be notified by March 20. The first version of the schedule will be published on April 2nd. Proposals can be done in English or Spanish. Proposals should be sent by March 10th at 23:59 UTC to iff(a)torproject.org. Proposals sent after the deadline or by other means will not be accepted. With the exception of artistic activities, the activities must be carried out within 1 hour between April 23 and 24. The session's facilitators of the Tor Village will have free ticket to the event. Unfortunately, in this first edition of the Village, the Tor Project cannot assist participants with travel expenses or other costs. Proposal -------- Be sure to include the following, Proposal title: Abstract: (max 100 words) Proposal description (max 500 words): Time: ________ (max 50 minutes) Availability: [ ] Only day 1 [ ] Only day 2 [ ] both Type of activity: [ ] Workshop [ ] Talk [ ] Discussion [ ] Other: ________ Speaker name / Organization name: Tech rider: what equipments do you need for your presentation? Language: [ ] English [ ] Spanish Some examples: - Sharing experience and challenges about Tor workshops and anonymity - Automation and deployment of onion services - Forming your Tor relay association - How to convince your organization or your university to run an exit node - Presentation of research results on users of Tor ecosystem tools - Analysis of results on the usability of the Tor Navigator - Art installation on how the Tor network works - Localization of Tor based tools - Good practices for journalists when using Tails - Application containers using Onion Services - Presentation of personas study on Tor users Questions? Contact us! ---------------------- In case of questions or doubts, contact us by email: iff(a)torproject.org or ask us during our weekly meetings: every monday, 1600 UTC, on #tor-meeting - irc.oftc.net. Or read how you can chat with us: https://support.torproject.org/get-in-touch/irc-help/

1 0

S30 Meeting on Tuesday February 11th 2020
by Gaba 11 Feb '20

11 Feb '20

Hi! We are meeting on February 11th for the S30 project [0]. The meeting with be at 1800 UTC in #tor-meeting, irc.oftc.net cheers, gaba [0] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 1

S27 Meeting today, Tuesday 7th January @ 15UTC
by Pili Guerra 11 Feb '20

11 Feb '20

Hi everyone, Happy New Year! We will be having our first meeting of the year for this project today. Looking forward to catching up and starting the final stretch for this project. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 5

Tails report for January 2020
by sajolida 11 Feb '20

11 Feb '20

https://tails.boum.org/news/report_2020_01/ Releases ======== - Tails 4.2 was released on January 7. - Tails 4.2.2 was released on January 14 (emergency release). - Tails 4.3 is scheduled for February 11. The following changes were introduced in Tails 4.2: - Improvements to automatic upgrades We worked on important improvements to the automatic upgrade feature, which is still one of your major pain points when using Tails: - Until now, if your version of Tails was several months old, you sometimes had to do 2 or more automatic upgrades in a row. For example, to upgrade from Tails 3.12 to Tails 3.16, you first had to upgrade to Tails 3.14. Starting with 4.2, direct automatic upgrades will be available from all prior versions to the latest version. - Until now, you could only do a limited number of automatic upgrades, after which you had to do a much more complicated "manual" upgrade. https://tails.boum.org/doc/upgrade/#manual Starting with 4.2, you will only have to do a manual upgrade between major versions, for example to upgrade to Tails 5.0 in 2021. - We made automatic upgrades use less memory. - We optimized a bit the size of the download when doing automatic upgrades. - We included several command line tools used by SecureDrop users to analyze the metadata of leaked documents on computers that cannot use the Additional Software feature: - PDF Redact Tools to redact and strip metadata from text documents before publishing - Tesseract OCR to convert images containing text into a text document - FFmpeg to record and convert audio and video - Open ~/Persistent/keepassx.kdbx by default when starting KeePassX. If this database does not exist yet, stop pointing to it in the list of recent databases. The following changes were introduced in Tails 4.2: - Update Tor Browser to 9.0.4. This fixes a critical vulnerability in the JavaScript JIT compiler of Firefox and Tor Browser. Mozilla is aware of targeted attacks in the wild abusing this vulnerability. This vulnerability only affects the standard security level of Tor Browser. The safer and safest security levels are not affected. - Avoid a 2-minutes delay when restarting after doing an automatic upgrade. (#17026) Code ==== - We fixed critical regressions that were introduced while improving automatic upgrades. - We started work on making the download of automatic upgrades more robust (#15875). - We fixed the long delay while rebooting after applying an automatic upgrade (#17026). - In order to make the development process a bit smoother: - We now use the tarball with all Tor Browser langpacks (#17400), instead of downloading a complete Tor Browser for every language. - Our build system is now able to cache the website build. Documentation and website ========================= - Göktürk Yüksek improved the dd command in the expert installation scenario to display progress (status=progress) and sync on-the-fly (oflag=direct). - We fixed the display of the output of rsync when doing a backup of the persistent volume. https://tails.boum.org/doc/first_steps/persistence/copy/ Infrastructure ============== - We made progress on our migration to GitLab. - We resumed work on upgrading our CI hardware (#16960). Funding ======= - We added ThinkPenguin as a partner. https://tails.boum.org/partners/ - We teared down the donation campaign. We raised around 100k€ from 2 000 donations. - We were invited to submit a full proposal for the joint grant proposal with Tor and the Guardian Project to the DRL Internet Freedom program. Hot topics on our help desk =========================== - A lot of users are complaining about Seahorse failing to import public keys. (#17183) - A few people reported graphic issues, mostly #16875, but also with Nvidia Turing. (#17155) - Some users are facing issues (#17388, #17430, #17418) with some network adapter since 4.1.1. (#17388, #17430, #17418) Translations ============ All the website --------------- fr: 86% (5293) strings translated, 3% strings fuzzy es: 51% (3134) strings translated, 4% strings fuzzy de: 34% (2143) strings translated, 10% strings fuzzy it: 30% (1852) strings translated, 8% strings fuzzy fa: 27% (1689) strings translated, 10% strings fuzzy pt: 22% (1359) strings translated, 8% strings fuzzy Core pages of the website ------------------------- fr: 93% (1695) strings translated, 4% strings fuzzy es: 90% (1636) strings translated, 2% strings fuzzy de: 64% (1168) strings translated, 16% strings fuzzy it: 60% (1094) strings translated, 18% strings fuzzy pt: 43% (792) strings translated, 14% strings fuzzy fa: 32% (596) strings translated, 14% strings fuzzy Metrics ======= - Tails has been started more than 856 922 times this month. This makes 27 643 boots a day on average. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing

1 0