diff options
Diffstat (limited to 'docs/source/locale/en/LC_MESSAGES/security.po')
| -rw-r--r-- | docs/source/locale/en/LC_MESSAGES/security.po | 50 |
1 files changed, 44 insertions, 6 deletions
diff --git a/docs/source/locale/en/LC_MESSAGES/security.po b/docs/source/locale/en/LC_MESSAGES/security.po index ef50754f..ac7f6a29 100644 --- a/docs/source/locale/en/LC_MESSAGES/security.po +++ b/docs/source/locale/en/LC_MESSAGES/security.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: OnionShare 2.3\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-09-09 19:15-0700\n" +"POT-Creation-Date: 2021-09-10 12:35-0700\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -70,7 +70,7 @@ msgid "" "services allowed the attacker to discover private ``.onion`` addresses. " "If an attack discovers a private OnionShare address, they will also need " "to guess the private key used for client authentication in order to " -"access it (unless the OnionShare user chooses make their serivce public " +"access it (unless the OnionShare user chooses make their service public " "by turning off the private key -- see :ref:`turn_off_private_key`)." msgstr "" @@ -86,10 +86,10 @@ msgid "" "through an email message monitored by an attacker), an eavesdropper can " "tell that OnionShare is being used. If the eavesdropper loads the address" " in Tor Browser while the service is still up, they can access it. To " -"avoid this, the address must be communicateed securely, via encrypted " -"text message (probably with disappearing messages enabled), encrypted " -"email, or in person. This isn't necessary when using OnionShare for " -"something that isn't secret." +"avoid this, the address must be communicated securely, via encrypted text" +" message (probably with disappearing messages enabled), encrypted email, " +"or in person. This isn't necessary when using OnionShare for something " +"that isn't secret." msgstr "" #: ../../source/security.rst:24 @@ -310,3 +310,41 @@ msgstr "" #~ " public - see :ref:`turn_off_private_key`)." #~ msgstr "" +#~ msgid "" +#~ "**If an attacker learns about the " +#~ "onion service, it still can't access " +#~ "anything.** Prior attacks against the " +#~ "Tor network to enumerate onion services" +#~ " allowed the attacker to discover " +#~ "private ``.onion`` addresses. If an " +#~ "attack discovers a private OnionShare " +#~ "address, they will also need to " +#~ "guess the private key used for " +#~ "client authentication in order to access" +#~ " it (unless the OnionShare user " +#~ "chooses make their serivce public by " +#~ "turning off the private key -- see" +#~ " :ref:`turn_off_private_key`)." +#~ msgstr "" + +#~ msgid "" +#~ "**Communicating the OnionShare address and " +#~ "private key might not be secure.** " +#~ "Communicating the OnionShare address to " +#~ "people is the responsibility of the " +#~ "OnionShare user. If sent insecurely " +#~ "(such as through an email message " +#~ "monitored by an attacker), an " +#~ "eavesdropper can tell that OnionShare is" +#~ " being used. If the eavesdropper " +#~ "loads the address in Tor Browser " +#~ "while the service is still up, " +#~ "they can access it. To avoid this," +#~ " the address must be communicateed " +#~ "securely, via encrypted text message " +#~ "(probably with disappearing messages enabled)," +#~ " encrypted email, or in person. This" +#~ " isn't necessary when using OnionShare " +#~ "for something that isn't secret." +#~ msgstr "" + |