Opened 4 weeks ago

Closed 4 weeks ago

#21342 closed task (fixed)

Move meek-azure to the meek.azureedge.net backend and cymrubridge02 bridge.

Reported by: dcf Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: meek tbb-bridges TorBrowserTeam201701R
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

meek-azure has a new backend infrastructure and bridge:

https://lists.torproject.org/pipermail/tor-project/2017-January/000906.html

This patch migrates to the new settings. This is the new bridge line:
meek 0.0.2.0:3 97700DFE9F483596DDA6264C4D7DF7641E1E39CE url=https://meek.azureedge.net/ front=ajax.aspnetcdn.com

We plan to similarly migrate meek-amazon in the future. However I think
it is prudent to only do meek-azure first, in order to limit the impact
of any unexpected failure in using the new bridge.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEeXoyauxKR4rwUMw64rk9gVzTiOUFAliMaaYACgkQ4rk9gVzT
iOWBGA/+IW7VWQLBU8lLq2qy55t8YeMHPqTZWdmSF4GGag9CdOIxWbrr34BeCFUT
TZUVpxsOldHwnoxRvvJ08UB0DdfJU3c/tWlWNMl8HzRH/GkpJli6ZqP6aJTElY7p
uFzw3Z0X+pplHcUednd8cSpd9ec+Rshbxd2K2PJlBhICthQPzavXbVrqwHucDgFR
MaKq/RsWaIBf3WO8QdCpAgTh8TPMgbmhswHImJPw3Sl/VvYJf3L899l7Yg1UHKZv
03S234v5hB+c+rTIIq2JMkQzDDlkOXQBCB6EpsiyeRyCWcsmy4KQ68YnG0CZVvm+
MpvOTpUEoN8EWPmoeNLhBQ3B0iBvV60PXHKzdKj9ZJnxRpGcXhjdopUVHbrqvmuv
xMrJOP6TOYY/LuxKvMzz+YCk8UWYCuqns3+Vx1uZ2ubPpEWyJImMZKiLi/yujZ0P
vM5e12eou8MhwYIRym1PFj3ymwTo9GPM2sz536o5fhMyUvvmfYEN+ib+AFQqyOnL
s/yVarDT0//8go5NkJUWaL+LfMUQyUb9ikLAWyeEYjtLTvHYiOLFf4QkEfEke08V
ru/M8rGwYCI7ZebweP3P2QxOF3+uzxERkB2+RoF3QXmeaqGrz+qmJf7HfJq0bOgO
n/bxNq5RvE2BliHJZ+AijKucrMIvWsNRKFAD4RpP0Gckomyv3nw=
=w57n
-----END PGP SIGNATURE-----

Child Tickets

Attachments (1)

0001-Move-meek-azure-to-the-meek.azureedge.net-backend-an.patch.gz (909 bytes) - added by dcf 4 weeks ago.

Download all attachments as: .zip

Change History (3)

comment:1 Changed 4 weeks ago by dcf

  • Keywords TorBrowserTeam201701R added
  • Status changed from new to needs_review

I had to gzip the patch because Trac thought it was spam:

Content contained these blacklisted patterns: '1[ -\.]?8[ -\.]?[045678][ -\.]?[045678][ -\.]?[0-9].?[0-9].?[0-9].?[0-9]?[0-9].?[0-9].?[0-9]'

comment:2 Changed 4 weeks ago by gk

  • Resolution set to fixed
  • Status changed from needs_review to closed

Applied to master and hardened-builds (commits 92c82fb6b5aa06c9ed4c304d47aca1bf3e92d1ca and 6bd92c5d7a8052b4603a3d0e2f9e412f8ac0d4b1), thanks.

Note: See TracTickets for help on using tickets.