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