You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 11, 2019. It is now read-only.
Please run through the test cases in the following PR: 855c5a4
Original Reported Issue
If a user enters https://nyttips4bmquxfzw.onion/ into the URL bar of a tab without Tor, they probably actually wanted to reach it over Tor, and probably didn't want to notify their unfriendly neighbourhood DNS server that they're about to leak something in exchange for a name resolution error page.
For .onion sites entered into the URL bar, we should consider either
automatically transplanting them into a private tab with Tor enabled, or
notifying them that the tab is not using Tor and can't reach onion services.
For .onion sites retrieved during page load, we should consider blocking them immediately.
Consider, for example, testing a locally served version of an onion site, which has secret links to other onion sites. (Old-style short onion names like the NYT Tips one above are not kept secret by the Tor network, but the next generation onion names are kept secret.)