Hello everyone,
Similar to the past few months most of my work last month focussed on
helping users in regions where Tor is censored, which includes helping
users with instructions to download Tor Browser binaries from GetTor
and/or official mirrors, verifying Tor Browser's GPG signature, help
with using censorship circumvention methods that works best for them and
overall troubleshooting. We saw a massive uptick in support requests
from Chinese speaking users most of which can be attributed …
[View More]to the
backlog of tickets I had to answer coming from the holiday break.
I also made some minor documentation updates, 1) updated articles for
Tor Browser 13.5 legacy updates with Tor Browser 13.5.11[0], 2) Onion
service documentation on the Community Portal[1].
Following is a more detailed report about the tickets our user support team
worked on last month.
# Frontdesk (email user support channel)
* 627(↓) RT tickets created
* 780(↑) RT tickets resolved
Tickets by topics and numbers:
1. 425(↑) RT tickets: instructions to circumvent censorship for Chinese
speaking users.
2. 191(↓) RT tickets: circumventing censorship in Russian speaking countries.
3. 11(↓) RT tickets: WebTunnel bridges campaign.
4. 5(↓) RT tickets: help with installing Tor Browser for Desktop.
5. 5(↓) RT tickets: questions about how Tor works - is my IP visible when using Tor?
what application level protections I get when using Tor Browser? what are
'Security Levels' in the Tor Browser etc.
6. 5(↓) RT tickets: reports of websites blocking Tor connections.
7. 5(↑) RT tickets: questions about how one can contribute to Tor - code,
documentation, localization, etc.
8. 5(↑) RT tickets: questions about onion services and how to access them.
9. 4(↑) RT tickets: circumventing censorship with Tor in Farsi.
10. 4(↓) RT tickets: help with troubleshooting existing Tor Browser install on
Desktop (Windows, macOS and Linux).
11. 4(↑) RT tickets: reports of anti-virus software blocking Tor Browser
(these were false alarms, see https://support.torproject.org/tbb/tbb-10/)
12. 3(↑) RT tickets: help with setting up a Snowflake proxy.
13. 3(↑) RT tickets: questions about setting up a bridge relay.
14. 3(↑) RT tickets: help with using bridges and snowflake with little-t-tor.
15. 2(↓) RT tickets: reports of a fake apps on iOS AppStore masquerading as
official Tor Browser.
16. 2(↑) RT tickets: help with troubleshooting Tor Browser Android.
17. 1(↓) RT ticket: instructions to download Tor Browser 13.5 legacy for legacy
operating systems.
# Telegram, WhatsApp and Signal Support channel
* 856(↓) tickets resolved
Breakdown:
* 839(↓) tickets on Telegram
* 17(↓) tickets on WhatsApp
* 0(↓) tickets on Signal
Tickets by topics and numbers:
1. 579(↓) tickets: circumventing censorship in Russian speaking countries.
2. 30(↑) tickets: instructions to circumvent censorship for Chinese speaking users.
3. 12(↓) tickets: circumventing censorship with Tor in Farsi.
4. 14(-) tickets: helping users on iOS, using Onion Browser or Orbot, to use censorship
circumvention methods.
5. 5(↓) tickets: help with troubleshooting Tor Browser Desktop on Windows, macOS and Linux.
6. 4(↓) tickets: help with instructions to use bridges with Tails.
7. 4(↑) tickets: questions about onion services and how to access them.
8. 2(-) tickets: users seeing a "proxy refused" error when visiting websites on Tor Browser
for Android using Samsung devices.[2]
9. 1(↓) ticket: instructions on how to get Tor Browser binaries from GetTor.
10. 1(↓) tickets: instructions to download Tor Browser 13.5 legacy for legacyoperating systems.
11. 1(↑) ticket: question about the differences in various security levels in the Tor
Browser.
12. 1(-) ticket: help with using bridges and snowflake with little-t-tor.
13. 1(↑) ticket: report of a fake app on iOS AppStore masquerading as official Tor Browser.
# Highlights from the Tor Forum
1. Configuring little-t-tor to use pluggable transports.[3]
2. JavaScript and extensions / add-ons with Tor Browser.[4]
Note: (↑), (↓) and (-) are indicating if the number of tickets we
received for these topics have been increasing, decreasing or have been
the same from the previous month respectively.
best,
e.
[0]: https://gitlab.torproject.org/tpo/community/support/-/issues/40178
[1]: https://gitlab.torproject.org/tpo/web/community/-/merge_requests/412
[2]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42714
[3]: https://forum.torproject.org/t/webtunnel-bridges-work-with-tor-browser-but-…
[4]: https://forum.torproject.org/t/struggling-with-javascript-and-add-ons-in-to…
[View Less]
Hello,
The Global South mailing list has been quiet for some time, and the Tor community team has decided to repurpose it for Tor partners in the Global South.
Moving forward, we will use it to share updates on activities such as online meetups, Privacy Resilience Grants, in-person training-of-trainers opportunities (Tor Training Academy), and more.
The list will be refreshed today, Tuesday, February 4th. We invite everyone to join the Tor forum: https://forum.torproject.org/
Thank you,
Za'atar
Hi,
User-visible
============
I've reviewed and supported the work of my team-mates on a number of
high priority user-visible improvements.
User-invisible
==============
Apart of the usual amount of KTLO work:
- I've been coordinating the search for new maintainers for Metadata
Cleaner:
https://forum.torproject.org/t/metadata-cleaner-is-looking-for-a-new-co-mai…
- I have automated some Git operations that were previously done
manually every time we merged changes into our main
…
[View More] development branch.
- I have fixed several vulnerabilities that were found by Radically
Open Security as part of their recent security audit of Tails.
Sadly, some of them were similar to those found during their
previous audit. We want to learn from this, stay tuned!
- I created automation that ensures we won't reintroduce 1 of the
types of vulnerability that were found during this audit.
Team lead
=========
- We, the Tails Team, have been working on our priorities for 2025
together with sajolida (UX). I'll publish a cleaned up
version shortly.
- I've learned how the grant reporting process works at Tor.
- I've deleted or updated public documentation for Tails contributors
that was made obsolete by the merge with Tor.
Accounting
==========
I've reviewed partial books from 1 of Tails' previous fiscal sponsors,
as part of the transition to Tails' new nest, the Tor project.
Cheers,
--
intrigeri
[View Less]
Hi! Below is my January’25 report!
In January, I resolved a total of 904 tickets, a decrease of 775 from
the previous month (total: 1679):
- RT (frontdesk@tpo) - 191 (↓28)
- Telegram (@TorProjectSupportBot) - 712 (↓747)
- WhatsApp (+447421000612) - 1 (1)
- Signal (+17787431312) - 0 (0).
My main focus in January (and always) was supporting Russian-speaking
users in bypassing internet censorship. So I shared censorship
circumvention instructions, helped users …
[View More]resolve any issues they are
facing with Tor Browser, and collected their feedback on what worked for
them and what didn’t. I also took part in Tor Forum moderation and
worked on reviewing Google Play Store users' reviews.
For the first in the last six months, we observed a decrease in support
tickets from Russian-speaking users. Despite this decrease, the number
of tickets is still higher than in July-2024, when new censorship
activities by Roskomnadzor were detected[1]. I created a new ticket to
track censorship in Russia in 2025[2].
## Elections in Belarus
In January there were Presidential Elections in Belarus [3]. On the eve
of the elections many VPN services and websites were blocked in the
country [4]. It seems Tor remained accessiblewith bridges[5],however
some users reported difficulties in finding working bridges.
*##**Google Play Reviews for Tor Browser**(TBA)**and Tor Browser
Alpha**for Android*
- Tor Browser for Android (TBA) had a Google Play rating of 4.389 (↑)
stars in January 2025, which is higher than in December.
- Tor Browser for Android (TBA) got 774 (↑17) reviews out of 60,429 for
the lifetime.
- Tor Browser for Android Alpha (TBA-Alpha) app had a rating of 4.219
(↓) which is lower than in December.
- In January, Tor Browser for Android (TBA-Alpha) got 37 (0) reviews out
of 8,448 for the lifetime.
## Most common issues on the Google Play store reviews
- “Tor Browser doesn’t work”: - often from Russian users, who are
struggling to find a way to connect to Tor;
- “Tor speed is too slow”: I use a template asking to refresh the Tor
circuit or contact Tor Browser support.
In the reviews I also encountered an issue of Tor Browserfor
Androidfreezes when used on Realme GT NEO 3 smartphone[6].
[1]
https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss…
[2]
https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss…
[3] https://en.wikipedia.org/wiki/2025_Belarusian_presidential_election
[4] https://news.zerkalo.io/life/89461.html?tg=4
[5]
https://metrics.torproject.org/userstats-bridge-combined.html?start=2024-10…
<https://metrics.torproject.org/userstats-bridge-combined.html?start=2024-10…>
[6]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43444
[View Less]
Hello tor-project@,
the following contains a summary of the work that I have done in January 2025.
## onionmasq
* Integration test for the isolation cookie feature
* Requires the use of connected UDP for the existing tests
* Wrote unit test for the `config` module
* Wrote unit test for the `scaffolding` module
* Added IPv6 integration tests alongside all existing IPv4 integration tests
* This achieves a full dual-stack testing environment
* Added a feature to disable file system …
[View More]permission checks
* This feature is crucial for CI integration
* Fixed a bug in the arti documentation alongside
* **Added integration tests to CI**
* Many thanks to micah@ for providing a privileged container
* Gives reproducible coverage numbers which is great, currently at >80%
* Replaced loopback IP addresses in the integration test suite with real but private IPs
* Replaces `127.0.0.1` with `172.23.39.177/12`
* Replaces `::1` with `fd5b:955e:ad4d::`
* Both IPs have no deep meaning and were randomly generated, with input given by Diziet
* Disabled the use of namespaces in CI, as isolation makes no sense there
* Fixed a clippy warning
* Upgraded various dependencies
* More or less finished providing basic test infrastructure
* We are currently slightly above 80% coverage, doing more is possible, but probably not sustainable,
due to the logarithmic nature of increasing test coverage
## oniux
* Began working on a very new prototype for replacing `torsocks` with a namespace based approach
* This is still very much WIP, the design concept is done and I am currently working on a prototype
* It is open space and I will keep this mailing list informed about further progress
* Name is also WIP 🙂
Thank You
Clara
[View Less]
Hi everyone!
Here is my status report for January 2025.
At the beginning of this month, I continued fixing the letterboxing
tests needed for the uplift process. There were several
platform-specific failures, so I had to set up a Windows build and test
environment for Firefox. It was the first time (we usually cross-compile
Tor Browser), and it took me some time.
Eventually, I got the Bug [0] to add some letterboxing exemptions
landed. Then, I opened a stack of patches (authored by ma1) on …
[View More]
Phabricator for the next Bug [1]. They have not been merged, yet,
because some parts still need the desktop theme reviewers' approval.
I also continued to help formalize the RR rebase process, and we merged
the first version [2]. After that, I created the first MR to start this
process, with the rebase of our patches onto Firefox 129 [3].
I checked the Firefox release calendar [4], and I suggested we keep a
pace of one RR rebase every week. If we manage to, we will reach
upstream by the end of March, with the rebase onto Firefox 138, and we
will have some time in case we have problems with some versions since
our objective is to be in sync with Firefox 129b1, which is scheduled
for around the end of April.
This month, I also tried to continue the fingerprinting fight effort,
which involved some investigations that eventually resulted in small tasks.
I started with v-sync on Wayland after we got an issue about possible
refresh rate leaks [5].
Another task was controlling our macOS font allow list [6]. I had to
verify some details in various macOS versions, and eventually, I will
have to ask about Japanese fonts to Mozilla experts.
Then, I started investigating why new windows are rounded incorrectly
[7] and I briefly checked the overlay scrollbars [8].
Apart from this, I also helped with the regular releases. I rebased
alpha onto 128.6.0esr at the beginning of the month, and I prepared the
14.5a2 release. Then, at the end of the month, I rebased stable and
alpha onto 128.7.0esr and legacy onto 115.20.0esr.
Finally, I started writing an uplift wish list for ESR 140 [9].
Best,
Pier
[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1555815
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1556016
[2]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests…
[3]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests…
[4] https://whattrainisitnow.com/
[5]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43236
[6]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43378
[7]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43205
[8]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/22137
[9]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40789#n…
[View Less]
Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2025/tor-meeting.2025-01-30-16.00.html
And our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday,Feb 02 16:00 UTC
Facilitator: meskio
^^^(See Facilitator Queue at tail)
Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC
(channel is logged while meetings are in progress)
This week's …
[View More]Facilitator: shelikhoo
== Goal of this meeting ==
Weekly check-in about the status of anti-censorship work at Tor.
Coordinate collaboration between people/teams on anti-censorship at the
Tor Project and Tor community.
== Links to Useful documents ==
* Our anti-censorship roadmap:
*
Roadmap:https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards
* The anti-censorship team's wiki page:
*
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home
* Past meeting notes can be found at:
* https://lists.torproject.org/pipermail/tor-project/
* Tickets that need reviews: from projects, we are working on:
* All needs review tickets:
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s…
* Project 158 <-- meskio working on it
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na…
== Announcements ==
* snowflake-broker.azureedge.net is still working, a week after the
announced shutdown date.(It still work at Jan 30)
curl -s -i https://snowflake-broker.azureedge.net/amp/client/
== Discussion ==
== Actions ==
== Interesting links ==
* "Identifying VPN Servers through Graph-Represented Behaviors"
* https://dl.acm.org/doi/10.1145/3589334.3645552
* https://dl.acm.org/doi/pdf/10.1145/3589334.3645552
* https://github.com/chenxuStep/VPNChecker
== Reading group ==
* We will discuss "" on
*
* 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.
Help with:
- Something you need help with.
cecylia (cohosh): 2025-01-30
Last week:
- debugged problem with tor conjure PT getting invalid addresses
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conj…
- reviewed conjure merge requests
- made more improvements to phantombox, the conjure test
environment
This week:
- support conjure work
- take a look at potential snowflake orbot bug
- https://github.com/guardianproject/orbot-android/issues/1183
- maybe do some lox work
dcf: 2025-01-23
Last week:
- tracked status of snowflake-broker.azureedge.net after
announced date of Edgio shutdown
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- helped debug reported "AMP cache rendezvous doesn't work in
China"
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
Next week:
- open issue to have snowflake-client log whenever KCPInErrors
is nonzero
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- parent:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- open issue to disable /debug endpoint on snowflake broker
Help with:
meskio: 2024-01-30
Last week:
- investigate issues on TorBrowser in Iran (tor-browser#43454)
- config repositories in irc tor bot
- grant writting and review
Next week:
- containarize rdsys
Shelikhoo: 2024-01-30
Last Week:
- [Refine] Unreliable+unordered WebRTC data channel transport
for Snowflake rev2 (cont.)(
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
) improvements
- Merge request reviews
Next Week/TODO:
- Merge request reviews
- [Test] Unreliable+unordered WebRTC data channel transport for
Snowflake rev2 (cont.)(
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
) improvements
onyinyang: 2025-01-30
Last week(s):
- Got conjure up and running locally! (Thanks cohosh!)
- uTLS implemented for conjure
- moved uTLS library to ptutil
- started work on ampcache
Next week:
- continue on alternative registration methods (ampcache, sqs)
- Add decoy registration option
As time allows:
- Continue work on implementing issuer efficiency for
check-blockage and trust-promotion protocols
- Work on outstanding milestone issues:
- key rotation automation
Later:
pending decision on abandoning lox wasm in favour of some kind
of FFI?
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096):
- add pref to handle timing for pubkey checks in Tor browser
- add trusted invitation logic to tor browser integration:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974
- improve metrics collection/think about how to show Lox is
working/valuable
- sketch out Lox blog post/usage notes for forum
(long term things were discussed at the meeting!):
- brainstorming grouping strategies for Lox buckets (of
bridges) and gathering context on how types of bridges are
distributed/use in practice
Question: What makes a bridge usable for a given user, and
how can we encode that to best ensure we're getting the most appropriate
resources to people?
1. Are there some obvious grouping strategies that we
can already consider?
e.g., by PT, by bandwidth (lower bandwidth bridges
sacrificed to open-invitation buckets?), by locale (to be matched with a
requesting user's geoip or something?)
2. Does it make sense to group 3 bridges/bucket, so
trusted users have access to 3 bridges (and untrusted users have access
to 1)? More? Less?
theodorsm: 2025-01-30
Last weeks:
- Testing Tor Build with covert-dtls (troubleshooting
becoming DTLS client with ICE and different NAT/host types).
Next weeks:
- Update covert-dtls to handle new DTLS extensions in
recent browsers
- Write instructions on how to configure covert-dtls with
snowflake client
- Fix merge conflicts in MR
(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…).
- Condensing thesis into paper (on hold)
Help with:
- Test stability of covert-dtls in snowflake
Facilitator Queue:
meskio onyinyang shelikhoo
1. First available staff in the Facilitator Queue will be the
facilitator for the meeting
2. After facilitating the meeting, the facilitator will be moved to the
tail of the queue
[View Less]
Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2025/tor-meeting.2025-01-23-16.04.html
And our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday,January 30 16:00 UTC
Facilitator: shelikhoo
^^^(See Facilitator Queue at tail)
Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC
(channel is logged while meetings are in progress)
This week'…
[View More]s Facilitator: onyinyang
== Goal of this meeting ==
Weekly check-in about the status of anti-censorship work at Tor.
Coordinate collaboration between people/teams on anti-censorship at the
Tor Project and Tor community.
== Links to Useful documents ==
* Our anti-censorship roadmap:
*
Roadmap:https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards
* The anti-censorship team's wiki page:
*
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home
* Past meeting notes can be found at:
* https://lists.torproject.org/pipermail/tor-project/
* Tickets that need reviews: from projects, we are working on:
* All needs review tickets:
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s…
* Project 158 <-- meskio working on it
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na…
== Announcements ==
* BridgeStatus's Snowflake bridge test output will change after
deployment of
* Use gitlab circumvention setting for snowflake bridge line update
*
https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/…
* Be sure to check if any automated script is still working
correctly
* snowflake-broker.azureedge.net is still working, a week after the
announced shutdown date.
curl -s -i https://snowflake-broker.azureedge.net/amp/client/
== Discussion ==
== Actions ==
== Interesting links ==
== Reading group ==
* We will discuss "" on
*
* 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.
Help with:
- Something you need help with.
cecylia (cohosh): 2025-01-23
Last week:
- worked on some phantombox (conjure test environment) improvements
- https://gitlab.torproject.org/cohosh/phantombox/-/issues/2
- fixups to switching to local storage for snowflake badges
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- some reviews and gitlab todos
This week:
- asn mapping geoip feature
dcf: 2025-01-23
Last week:
- tracked status of snowflake-broker.azureedge.net after
announced date of Edgio shutdown
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- helped debug reported "AMP cache rendezvous doesn't work in
China"
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
Next week:
- open issue to have snowflake-client log whenever KCPInErrors
is nonzero
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- parent:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- open issue to disable /debug endpoint on snowflake broker
Help with:
meskio: 2024-01-23
Last week:
- debug a segfault in country based metrics to the snowflake
proxy (snowflake!482)
- debug why metrics.torproject.org doesn't display distributor
metrics (rdsys#235)
- keep up with snowflake debian dependencies (snowflake#40410)
- deploy onionsproutsbot (onionsproutsbot#66)
- investigate why we distribute non working bridges (rdsys#254)
- simple refactor fixes on rdsys bridge tests (rdsys!454)
- review and update P146 report
- triage the long queue of open issues (there are still some
snowflake ones missing)
Next week:
- snowflake debian package
Shelikhoo: 2024-01-23
Last Week:
- [Pending] snowflake broker update/reinstall(cont.):
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
- [Awaiting Review] Unreliable+unordered WebRTC data channel
transport for Snowflake rev2 (cont.)(
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
) improvements
- Merge request reviews
- Automate bridgeline update for
snowflake(https://gitlab.torproject.org/tpo/anti-censorship/connectivity-me…
)
- Use assume reachable for webtunnel bridges to avoid exporting OR
port(https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measure…
- Update readme to include migration notice
(https://gitlab.torproject.org/tpo/anti-censorship/docker-snowflake-proxy/-/…
)
-
Next Week/TODO:
- Merge request reviews
- [Resume] Unreliable+unordered WebRTC data channel transport
for Snowflake rev2 (cont.)(
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…
) improvements
- [Deployment] Automate bridgeline update for snowflake
onyinyang: 2025-01-23
Last week(s):
- Get conjure up and running (at least locally)
- WIP Conjure stuff for Project 173
Next week:
- Continue on getting conjure up and running (at least locally)
- implement utls for conjure
- start implementation of alternative registration methods
As time allows:
- Continue work on implementing issuer efficiency for
check-blockage and trust-promotion protocols
- Work on outstanding milestone issues:
- key rotation automation
Later:
pending decision on abandoning lox wasm in favour of some kind
of FFI?
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096):
- add pref to handle timing for pubkey checks in Tor browser
- add trusted invitation logic to tor browser integration:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974
- improve metrics collection/think about how to show Lox is
working/valuable
- sketch out Lox blog post/usage notes for forum
(long term things were discussed at the meeting!):
- brainstorming grouping strategies for Lox buckets (of
bridges) and gathering context on how types of bridges are
distributed/use in practice
Question: What makes a bridge usable for a given user, and
how can we encode that to best ensure we're getting the most appropriate
resources to people?
1. Are there some obvious grouping strategies that we
can already consider?
e.g., by PT, by bandwidth (lower bandwidth bridges
sacrificed to open-invitation buckets?), by locale (to be matched with a
requesting user's geoip or something?)
2. Does it make sense to group 3 bridges/bucket, so
trusted users have access to 3 bridges (and untrusted users have access
to 1)? More? Less?
theodorsm: 2025-01-22 (AFK for meeting 01-23)
Last weeks:
- Testing Tor Build with covert-dtls
Next weeks:
- Update covert-dtls to handle new DTLS extensions in
recent browsers
- Write instructions on how to configure covert-dtls with
snowflake client
- Fix merge conflicts in MR
(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…).
- Condensing thesis into paper (on hold)
Help with:
- Test stability of covert-dtls in snowflake
Facilitator Queue:
meskio onyinyang shelikhoo
1. First available staff in the Facilitator Queue will be the
facilitator for the meeting
2. After facilitating the meeting, the facilitator will be moved to the
tail of the queue
--
---
onyinyang
GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036
[View Less]