- anti-censorship-team - lists.torproject.org

Meek/Snowflake/Moat fronts for older Android devices?
by Michael Rogers 05 Feb '25

05 Feb '25

Hi all, Devices running versions of Android older than 7.1.1 can't verify certificates signed with Let's Encrypt's ISRG Root X1 root certificate, so they can't connect to domain fronts that use such certificates. [1] These devices (released in 2016 or earlier) still make up nearly 5% of active Android devices. [2] There was a workaround in place at one point -- cross-signing Let's Encrypt certificates with a different, expired root certificate and relying on Android not to check the expiry date -- but I believe the cross-signature expired in early 2024. [3] With the loss of Fastly and Azure, the only remaining fronts for Meek and Snowflake in the default config served by Moat will be cdn77.com and phpmyadmin.net, both of which use Let's Encrypt certificates that are signed with ISRG Root X1 and don't appear to be cross-signed. It looks like there's some work in progress to address this issue in Lyrebird by adding the relevant certificates, so hopefully Meek and Snowflake will work in a future Lyrebird release. But what about the initial connection to Moat? Orbot has moved from Fastly to CDN77 for its Moat front [4]. Are there any plans underway to make another front available, or should we move to CDN77 and plan for Moat being unavailable on older Android devices? Thanks, Michael [1] https://letsencrypt.org/2020/11/06/own-two-feet/ [2] https://apilevels.com/ [3] https://arstechnica.com/gadgets/2020/12/lets-encrypt-comes-up-with-workarou… [4] https://github.com/guardianproject/orbot/pull/1191/files

4 10

Deprecation of Azure CDN from Edgio (azureedge.net), replaced by Azure Front Door (azurefd.net), affects snowflake-broker.azureedge.net
by David Fifield 05 Feb '25

05 Feb '25

I got an email on 2024-12-05 saying that that Azure CDN from Edgio/Verizon is going to shut down sooner than expected. The shutdown date was supposed to be 2025-11-04, now it is 2024-01-15 (about one month from now). This affects (at least) snowflake-broker.azureedge.net, which was first set up and is still on Azure CDN with Edgio. I think that snowflake-broker.azureedge.net has not been used by this team since 2021 and https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_re…. But it is still getting some use from somewhere, as evidenced by the nonzero monthly bills: https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-co… Whatever is out there that is still using snowflake-broker.azureedge.net will likely stop working after 2025-01-15. > Date: 5 Dec 2024 17:03:50 +0000 > From: Microsoft Azure <azure-noreply(a)microsoft.com> > Subject: Urgent action required: Migrate workloads on Azure CDN from Edgio (formerly Verizon) before 15 January 2025 > > Migrate to Azure Front Door or other CDN services as soon as possible > to avoid service disruptions. > > Migrate workloads on Azure CDN from Edgio (formerly Verizon) before 15 > January 2025. > > You're receiving this notice because you're currently using Azure CDN > Standard/Premium from Edgio. > > All Azure CDN from Edgio customers must migrate their workloads to > Azure Front Door or other CDN services before 15 January 2025 as Edgio > has advised their platform is currently scheduled to be shut down by > that date. Migrate as soon as possible to avoid an imminent service > shut-down. > > On 31 October 2024, we sent you a notice advising that Azure CDN > Standard/Premium from Edgio (formerly Verizon) will be retired on > 4 November 2025, and that customers of this service must migrate their > workload(s) to a comparable service before this date to avoid service > interruptions. In that email we also advised given that Edgio filed > for Chapter 11 Bankruptcy on 9 September 2024, Microsoft cannot > guarantee that Edgio will continue to support this service through > 4 November 2025 as previously stated. Online references about Azure CDN with Edgio retirement: https://learn.microsoft.com/en-us/azure/cdn/edgio-retirement-faq https://azure.microsoft.com/updates?id=467688 I did try setting up a Front Door CDN profile (which is the recommended replacement for Edgio), following the migration instructions: https://learn.microsoft.com/en-us/azure/frontdoor/migrate-cdn-to-front-door I got the hostname: snowflake-broker-hadmaqbnc4dmcffs.z03.azurefd.net It works as an alias for the broker: curl -i https://snowflake-broker-hadmaqbnc4dmcffs.z03.azurefd.net/debug However, it apparently does not work with domain fronting, so is likely not actually useful. Front Door not working with domain fronting is consistent with prior announcements by Azure: https://github.com/net4people/bbs/issues/67

7 21

Fwd: Scheduled Client Panel & API Maintenance on December 3, 2024
by meskio 18 Dec '24

18 Dec '24

I got this email forwarded to me. It looks like there will be downtime in the Client Pannel of CDN77 what we use for domain fronting. > ---------- Forwarded message --------- > From: CDN77 <news(a)cdn77.com> > Date: Tue, Nov 26, 2024 at 9:35 AM > Subject: Scheduled Client Panel & API Maintenance on December 3, 2024 > To: accounting(a)torproject.org <accounting(a)torproject.org> > > > Due to schedule upgrades and maintenance, the CDN77 Client Panel and API > will be temporarily unavailable. > View in browser > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> > > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> > Docs & API > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> > Client > Panel > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> > > Dear Client, > > Due to schedule upgrades and maintenance, the CDN77 Client Panel and API > will be temporarily unavailable. Other affected services include purge & > prefetch requests, as well as attempts to modify or change CDN Resource > settings and configurations via API. > > Please schedule any important changes before this time, and plan ahead with > this scheduled maintenance in mind. This maintenance *will not affect your > traffic flow*; all content delivery will continue as normal. > > *When:* December 3, 2024, starting at 10:00 AM UTC > > *Expected Downtime:* Up to 15 minutes > > *Need assistance?* Our 24/7 support team will be available through our > website at www.cdn77.com > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> > . > > We apologize for any inconvenience and thank you for your understanding. > > Best Regards, > > *Juraj Kacaba* > > Head of Client Implementations > Email: support(a)cdn77.com > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> > > Sent by DataCamp Limited > 9 Coldbath Square, London, United Kingdom > Unsubscribe > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> > Contact > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> > Privacy > policy > <https://news.cdn77.com/tb/cl/eyJ2Ijoie1wiYVwiOjUwNjYwMyxcImxcIjoxMzkwNzQzNj…> -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.

2 1

Anyone have a copy of the v0.9.0 Snowflake WebExtension CRX file?
by David Fifield 12 Dec '24

12 Dec '24

I just archived v0.9.0 and v0.9.1 of the Snowflake WebExtension: https://archive.org/details/snowflake-webextension-0.9.0 https://archive.org/details/snowflake-webextension-0.9.1 However, I neglected to download v0.9.0 from the Google Play Store before it got updated to v0.9.1, and I don't know of a way to download older version from the Google Play Store. What I've done for v0.9.0 is uploaded Shelikhoo's submitted build-webext-chromium_v3.zip from https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…. But ideally I'd like to have the CRX file that is digitally signed by Google. Does someone maybe have v0.9.0 still installed, or else know how to download an older version? What I do to download the current version is fetch the URL https://clients2.google.com/service/update2/crx?response=redirect&prodversi…

2 3

Status of snowflake covert-dtls-test?
by David Fifield 09 Dec '24

09 Dec '24

Recently there have been problems with Snowflake connectivity in Russia. WebRTC data connections are being established, but then stop working after some amount of traffic is exchanged. cohosh has investigated and whatever the cause is, it's not straightforward DTLS fingerprinting. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Theodor, what's the status of your covertDTLS patch to Snowflake? https://gitlab.torproject.org/theodorsm/snowflake/-/tree/covert-dtls-test Is it ready to be run as a test client? If so, can you provide brief instructions on how to do it? Snowflake recently updated to pion/webrtc/v4, which I seem to recall was a blocker for covertDTLS integration. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Here's where we discussed this topic in the team meeting today. https://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-11-21-16.00.lo… https://lists.torproject.org/mailman3/hyperkitty/list/tor-project@lists.tor… P.S. I Cced the anti-censorship-team(a)lists.torproject.org mailing list.

2 2

Microsoft announces shutting down domain fronting attempts in Azure
by Cecylia Bocovich 18 Nov '24

18 Nov '24

It looks like Azure is going to shutdown domain fronting: https://www.microsoft.com/security/blog/2021/03/26/securing-our-approach-to… There isn't a time frame listed in the article, and I haven't gotten any notifications through my Azure account yet. Cecylia

7 9

goptlib v1.6.0
by David Fifield 14 Nov '24

14 Nov '24

I tagged v1.6.0 of goptlib. It has a bug fix (panic in DialOr) and a corrected test case. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/gopt… > == v1.6.0 > > Fixed a type assertion panic in DialOr that occurred when the network dial > failed. Patch by Rob Jansen. > https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/gopt… > > Enhanced the TestGetServerBindaddrs test to compare not only MethodName and > Addr, but also Options, and fixed a test case that expected the wrong Options. > Patch by Jack Wampler. > https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/gopt…

1 0

Relative usage of snowflake-01 and snowflake-02 bridges, October 2024
by David Fifield 04 Nov '24

04 Nov '24

This is just a note to observe that the usage of snowflake-01 and snowflake-02 appears to have reached an equilibrium in recent months, though the usage is still unequal. The users and especially bandwidth are recently highly correlated. But the country distribution still differs a lot. snowflake-01 is Iran first, Russia second; while snowflake-02 is Russia first, Iran second.

1 0

Vanilla bridges not available from bridges.torproject.org web interface
by Michael Rogers 04 Nov '24

04 Nov '24

Hi all, It seems that bridges.torproject.org is no longer serving vanilla bridges via the web interface. The following page (reached by selecting "none" in the transport dropdown) has no content: https://bridges.torproject.org/bridges?transport=0 Cheers, Michael

2 1

Reminder: mailman 3 upgrade imminent (TPA-RFC-71)
by Antoine Beaupré 29 Oct '24

29 Oct '24

Hi, As mentioned in early October, we're in the process of upgrading our main mail server, which includes upgrading to the shiny new Mailman 3 platform. We have, right now, a prototype mailman 3 server available at: https://lists-01.torproject.org/ It's hidden behind the usual "trivial" authentication (ask us on IRC if you don't remember what it is), but should otherwise work normally. I'm going to start by migrating the TPA mailing list and we'll be testing this for a couple of days, but, next week, I'll start migrating the other mailing lists (including this one!). If people want to jump in front of that train early and be part of the beta testers, then by all means I'm happy to have your mailing list be part of the early adopters. Be warned that Mailman 3 is a significant upgrade from Mailman 2. There are some great things (like unified authentication), and some less great things (like a more complex design and "shinier" web interface that might not be everyone's taste). As a reminder, we're doing this upgrade a little rushed because the main mail server is now unsupported for security upgrades. See the details of the proposal here: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-71-emerge… ... with the milestone tracking actual work issues in: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/16 (Sorry for cross-posting this, but this seems like it warrants wider distribution. As a rule of thumb, I selected mailing lists with public archives that had posts in October 2024, removing duplicates like anti-censorship-team and -alerts. I also suspect many of those mailing lists will refuse my message because I'm not subscribed, but I will have tried. :)) Phew! a. -- Antoine Beaupré torproject.org system administration

1 0

2025

2024

2023

2022

2021

2020

2019

anti-censorship-team