[tor-bugs] #28005 [Applications/Tor Browser]: Officially support onions in HTTPS-Everywhere
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Apr 2 10:08:15 UTC 2020
#28005: Officially support onions in HTTPS-Everywhere
-------------------------------------------------+-------------------------
Reporter: asn | Owner: tbb-
| team
Type: defect | Status:
| needs_review
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tor-hs, https-everywhere, network- | Actual Points: 18.5
team-roadmap-november, network-team-roadmap- |
2020Q1, ux-team, TorBrowserTeam202004R |
Parent ID: #30029 | Points: 20
Reviewer: mcs, sysrqb, antonela | Sponsor:
| Sponsor27-must
-------------------------------------------------+-------------------------
Comment (by acat):
> In any case, the current patch correctly adds .tor.onion as a new eTLD,
however maybe it should go further and add securedrop.tor.onion as an eTLD
because all sub-domains of securedrop.tor.onion are distinct origins. To
make this explicit, currently www.abc.net.au.securedrop.tor.onion has
(potentially) the same "origin" as www.2600.com.securedrop.tor.onion
because they share the same eTLD (.tor.onion).
I forgot addressing this. However, note the eTLD+1 is highlighted in the
urlbar, so adding `securedrop.tor.onion` does make a UX change in the
urlbar. For example, with that change for
`www.nytimes.com.securedrop.tor.onion` we will highlight
`com.securedrop.tor.onion` (instead of `securedrop.tor.onion` with the
current patch). But perhaps it's still the right thing to do, and this
issue is just a consequence of how the SecureDrop rules were defined.
In any case, this patch adds the securedrop.tor.onion eTLD:
https://github.com/acatarineu/tor-browser/commit/28005+8
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28005#comment:52>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list