[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #23247 [Applications/Tor Browser]: Communicating security expectations for .onion: what to say about different padlock states for .onion services
#23247: Communicating security expectations for .onion: what to say about different
padlock states for .onion services
-------------------------------------------------+-------------------------
Reporter: isabela | Owner:
| pospeselr
Type: project | Status:
| needs_review
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: ux-team, tor-hs, | Actual Points:
TorBrowserTeam201805R |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by gk):
Replying to [comment:61 pospeselr]:
> Not sure I'm following gk regarding the strings. The new onion-related
strings are not hard-coded in the Page Info dialog, but pull from
pippki.properties file using the pkiBundle.getBLAHString API (as does
every other string lookup).
That's right. But where does the translation come from? Like, how would
that string look like in a, say, arabic Tor Browser? Clearly, it does not
get translated by Mozilla as we only ship it in our patch set. But all our
translations are done on Transifex either via Torbutton or Tor Launcher.
Thus, the string is essentially hard-coded assuming the browser is falling
back to en-US in case it can't find a string for the required locale. It
might even break, not showing the dialog at all.
> Should I be doing something else?
We could try, see 5) in my comment:51.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23247#comment:64>
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