Meek config for TM
Hi all, While updating Briar's built-in bridge config from Moat I noticed that Moat's still listing the Azure front for Meek in TM - is it still working? Cheers, Michael
Hi Michael, Indeed, it looks like this is no longer working. We expected this after we got the notice but left up the configuration because it appeared to be working as of January 16th. I've just opened a merge request to remove the last azure-fronted meek bridge line from moat[0]. Though I did notice that in Tor Browser we updated the bridge line to use CDN77 without updating the name from meek-azure. I've opened an issue for that[1]. You can use this new builtin bridge instead, and we have another CDN77-fronted bridge that we distribute to users in TM through moat. meek_lite 192.0.2.20:80 url=https://1314488750.rsc.cdn77.org front=www.phpmyadmin.net utls=HelloRandomizedALPN [0] https://gitlab.torproject.org/tpo/anti-censorship/rdsys-admin/-/merge_reques... [1] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41... On 2025-02-03 08:17, Michael Rogers via anti-censorship-team wrote:
Hi all,
While updating Briar's built-in bridge config from Moat I noticed that Moat's still listing the Azure front for Meek in TM - is it still working?
Cheers, Michael
Quoting Cecylia Bocovich via anti-censorship-team (2025-02-04 22:11:43)
Indeed, it looks like this is no longer working. We expected this after we got the notice but left up the configuration because it appeared to be working as of January 16th. I've just opened a merge request to remove the last azure-fronted meek bridge line from moat[0].
Ups, I just did the same. I should have checked your MR before. Anyway it looks good to merge.
Though I did notice that in Tor Browser we updated the bridge line to use CDN77 without updating the name from meek-azure. I've opened an issue for that[1].
I did keep the name thinking that it will complicate things trying to change it. Thank you for opening an issue for that, let's see what the applications team think about it. -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.
Great, thank you! I'll update Briar's config and OnionShare will pick up the updates from Moat. Cheers, Michael On 04/02/2025 21:11, Cecylia Bocovich via anti-censorship-team wrote:
Hi Michael,
Indeed, it looks like this is no longer working. We expected this after we got the notice but left up the configuration because it appeared to be working as of January 16th. I've just opened a merge request to remove the last azure-fronted meek bridge line from moat[0]. Though I did notice that in Tor Browser we updated the bridge line to use CDN77 without updating the name from meek-azure. I've opened an issue for that[1].
You can use this new builtin bridge instead, and we have another CDN77- fronted bridge that we distribute to users in TM through moat.
meek_lite 192.0.2.20:80 url=https://1314488750.rsc.cdn77.org front=www.phpmyadmin.net utls=HelloRandomizedALPN
[0] https://gitlab.torproject.org/tpo/anti-censorship/rdsys-admin/-/ merge_requests/36 [1] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/ issues/41359
On 2025-02-03 08:17, Michael Rogers via anti-censorship-team wrote:
Hi all,
While updating Briar's built-in bridge config from Moat I noticed that Moat's still listing the Azure front for Meek in TM - is it still working?
Cheers, Michael
_______________________________________________ anti-censorship-team mailing list -- anti-censorship- team@lists.torproject.org To unsubscribe send an email to anti-censorship-team- leave@lists.torproject.org
participants (3)
-
Cecylia Bocovich -
meskio -
Michael Rogers