-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Bisq sites reachable via onion address #5
Comments
This issue should be transferred to the ops repo. What domains don't support Tor? mempool.space certainly does, and this is hard-coded in the pull-down combo box as well. |
Yes, mempool.space is reachable via and advertises its onion address in the HTTP headers (so when accessing mempool.space in Tor Browser, the address bar shows a hint ".onion available"). However all the BIsq doamins listed here (bisq-network/proposals#211 (comment)) do not. Technically, they area reachable via Tor -- but having their own onion address would mean traffic never leaves the Tor network. This would bring more privacy to users + would make Bisq resilient against DNS vulnerabilities (technical or operational, see bisq-network/proposals#211)
What's the recommended way to do that? Delete it here and re-add there? Or create new one there, link to this one? |
Bisq Websites:
Bisq Explorers:
|
bsq.bisq.services -> http://ydh7aqlup5k27mmlq5c7zmvqzvqxwgveykcf3clcbhhd6qlrjryg3uqd.onion/ |
@m52go good work, but you also need to send the
|
Done. |
Make sure all Bisq sites that currently rely on clearnet domains are also reachable via an onion address.
In addition, the sites could advertise the onion address via the
Onion-Location
HTTP header, which would make Tor Browser users be automatically notified of the onion address, each time they visit a Bisq site.See https://www.torproject.org/releases/tor-browser-95/ for details and screenshots.
See https://community.torproject.org/onion-services/advanced/onion-location/ for Apache and nginx config examples.
The text was updated successfully, but these errors were encountered: