Opened 15 months ago
Closed 15 months ago
#27469 closed defect (fixed)
Change the moat service URL
Reported by: | gk | Owned by: | tbb-team |
---|---|---|---|
Priority: | Very High | Milestone: | |
Component: | Applications/Tor Launcher | Version: | |
Severity: | Normal | Keywords: | TorBrowserTeam201809R, tbb-8.0.1-can |
Cc: | hiro | Actual Points: | |
Parent ID: | Points: | ||
Reviewer: | Sponsor: |
Description
We need to change the Moat service URL one additional time after we switched to azure. All in all we should use the following URLs from now on:
extensions.torlauncher.moat_service https://bridges.torproject.org/moat extensions.torlauncher.bridgedb_front ajax.aspnetcdn.com extensions.torlauncher.bridgedb_reflector https://onionquiche.azureedge.net/
Child Tickets
Change History (7)
comment:1 Changed 15 months ago by
Keywords: | tbb-8.0.1-can added |
---|
comment:2 Changed 15 months ago by
Keywords: | TorBrowserTeam201809R added; TorBrowserTeam201809 removed |
---|---|
Status: | new → needs_review |
comment:3 Changed 15 months ago by
Component: | Applications/Tor Browser → Applications/Tor Launcher |
---|
comment:4 Changed 15 months ago by
Here are the urls for 8.0.1
extensions.torlauncher.moat_service https://bridges.torproject.org/moat
extensions.torlauncher.bridgedb_front ajax.aspnetcdn.com
extensions.torlauncher.bridgedb_reflector https://onion.azureedge.net/
comment:5 Changed 15 months ago by
Thanks, I pushed a new branch bug_27469_v2
(https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_27469_v2&id=1db5a1ccddffe78c6b1ff242acfa628d9e9823e0) for review.
comment:7 Changed 15 months ago by
Resolution: | → fixed |
---|---|
Status: | needs_review → closed |
Thanks! Merged to master
(commit 1db5a1ccddffe78c6b1ff242acfa628d9e9823e0).
bug_27469
(https://gitweb.torproject.org/user/gk/tor-launcher.git/commit/?h=bug_27469&id=cf508c95ea9dac54fd26bb0c0126f8923b0e0c3a) in my public Tor Launcher repository has the change for review.Testing is a bit tricky right now, as the new service URL shows an error. But I assume that's fixed by just flipping some configuration on the server side.