[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #34212 [Circumvention/Wolpertinger]: Set up a domain-fronted end point for wolpertinger
#34212: Set up a domain-fronted end point for wolpertinger
--------------------------------------------+----------------------
Reporter: phw | Owner: phw
Type: task | Status: assigned
Priority: Medium | Milestone:
Component: Circumvention/Wolpertinger | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID: #32740
Points: 1 | Reviewer:
Sponsor: Sponsor30-can |
--------------------------------------------+----------------------
Censorship measurement platforms like OONI can request bridges to test
from wolpertinger's REST API. Some platforms may be unable to talk to
wolpertinger because it runs on bridges.torproject.org, which may be
blocked. (This isn't an issue for OONI because it intends to proxy
wolpertinger requests over its backend.)
We should set up a domain-fronted endpoint to fix this issue: In addition
to a direct connection to bridges.torproject.org/wolpertinger, censorship
measurement platforms should be able to use a domain front at
ajax.aspnetcdn.com.
After reading #27469 and #16650, I believe that we need to configure
another azure reflector, e.g., wolpertinger.azureedge.net, which is hooked
up to https://bridges.torproject.org/wolpertinger/.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/34212>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs