summaryrefslogtreecommitdiff
path: root/docs/source/locale/pt_BR/LC_MESSAGES/security.po
diff options
context:
space:
mode:
Diffstat (limited to 'docs/source/locale/pt_BR/LC_MESSAGES/security.po')
-rw-r--r--docs/source/locale/pt_BR/LC_MESSAGES/security.po136
1 files changed, 105 insertions, 31 deletions
diff --git a/docs/source/locale/pt_BR/LC_MESSAGES/security.po b/docs/source/locale/pt_BR/LC_MESSAGES/security.po
index 05816266..034e0a77 100644
--- a/docs/source/locale/pt_BR/LC_MESSAGES/security.po
+++ b/docs/source/locale/pt_BR/LC_MESSAGES/security.po
@@ -3,15 +3,16 @@
# This file is distributed under the same license as the OnionShare package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
-#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: OnionShare 2.3\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-12-13 15:48-0800\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"
+"Report-Msgid-Bugs-To: onionshare-dev@lists.riseup.net\n"
+"POT-Creation-Date: 2021-09-17 14:39-0700\n"
+"PO-Revision-Date: 2021-09-18 20:19+0000\n"
+"Last-Translator: souovan <souovan@protonmail.com>\n"
+"Language: pt_BR\n"
+"Language-Team: pt_BR <LL@li.org>\n"
+"Plural-Forms: nplurals=2; plural=n > 1\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
@@ -19,19 +20,23 @@ msgstr ""
#: ../../source/security.rst:2
msgid "Security Design"
-msgstr ""
+msgstr "Design de Segurança"
#: ../../source/security.rst:4
msgid "Read :ref:`how_it_works` first to get a handle on how OnionShare works."
msgstr ""
+"Leia :ref:`how_it_works` primeiro para entender como o OnionShare "
+"funciona."
#: ../../source/security.rst:6
msgid "Like all software, OnionShare may contain bugs or vulnerabilities."
msgstr ""
+"Como todos os softwares, o OnionShare pode conter erros ou "
+"vulnerabilidades."
#: ../../source/security.rst:9
msgid "What OnionShare protects against"
-msgstr ""
+msgstr "Contra o que o OnionShare protege"
#: ../../source/security.rst:11
msgid ""
@@ -42,6 +47,12 @@ msgid ""
"server for that too. This avoids the traditional model of having to trust"
" the computers of others."
msgstr ""
+"**Terceiros não tem acesso a nada que acontece no OnionShare.** Usar "
+"OnionShare significa hospedar serviços diretamente no seu computador. Ao "
+"compartilhar arquivos com OnionShare, eles não são carregados para nenhum"
+" servidor. Se você criar uma sala de chat OnionShare, seu computador atua"
+" como um servidor para ela também. Isso evita o modelo tradicional de ter"
+" que confiar nos computadores de outras pessoas."
#: ../../source/security.rst:13
msgid ""
@@ -53,6 +64,13 @@ msgid ""
"Browser with OnionShare's onion service, the traffic is encrypted using "
"the onion service's private key."
msgstr ""
+"**Os bisbilhoteiros da rede não podem espionar nada que aconteça no "
+"OnionShare durante o trânsito.** A conexão entre o serviço onion Tor e o "
+"Navegador Tor são criptografadas de ponta-a-ponta. Isso significa que os "
+"invasores de rede não podem espionar nada, exceto o tráfego criptografado"
+" do Tor. Mesmo se um bisbilhoteiro for um nó de encontro malicioso usado "
+"para conectar o navegador Tor ao serviço onion da OnionShare, o tráfego é"
+" criptografado usando a chave privada do serviço onion."
#: ../../source/security.rst:15
msgid ""
@@ -62,45 +80,47 @@ msgid ""
"Browser users, the Tor Browser users and eavesdroppers can't learn the "
"identity of the OnionShare user."
msgstr ""
+"**O anonimato dos usuários do OnionShare é protegido pelo Tor**. "
+"OnionShare e Navegador Tor protegem o anonimato dos usuários, os usuários"
+" do navegador Tor e bisbilhoteiros não conseguem descobrir a identidade "
+"do usuário OnionShare."
#: ../../source/security.rst:17
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, a password will be "
-"prevent them from accessing it (unless the OnionShare user chooses to "
-"turn it off and make it public). The password is generated by choosing "
-"two random words from a list of 6800 words, making 6800², or about 46 "
-"million possible passwords. Only 20 wrong guesses can be made before "
-"OnionShare stops the server, preventing brute force attacks against the "
-"password."
+"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 service public "
+"by turning off the private key -- see :ref:`turn_off_private_key`)."
msgstr ""
#: ../../source/security.rst:20
msgid "What OnionShare doesn't protect against"
-msgstr ""
+msgstr "Contra o que OnionShare não protege"
#: ../../source/security.rst:22
msgid ""
-"**Communicating the OnionShare address 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."
+"**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 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
msgid ""
-"**Communicating the OnionShare address might not be anonymous.** Extra "
-"precautions must be taken to ensure the OnionShare address is "
-"communicated anonymously. A new email or chat account, only accessed over"
-" Tor, can be used to share the address. This isn't necessary unless "
-"anonymity is a goal."
+"**Communicating the OnionShare address and private key might not be "
+"anonymous.** Extra precautions must be taken to ensure the OnionShare "
+"address is communicated anonymously. A new email or chat account, only "
+"accessed over Tor, can be used to share the address. This isn't necessary"
+" unless anonymity is a goal."
msgstr ""
#~ msgid "Security design"
@@ -242,3 +262,57 @@ msgstr ""
#~ "necessary unless anonymity is a goal."
#~ 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,"
+#~ " a password will be prevent them "
+#~ "from accessing it (unless the OnionShare"
+#~ " user chooses to turn it off "
+#~ "and make it public). The password "
+#~ "is generated by choosing two random "
+#~ "words from a list of 6800 words,"
+#~ " making 6800², or about 46 million"
+#~ " possible passwords. Only 20 wrong "
+#~ "guesses can be made before OnionShare"
+#~ " stops the server, preventing brute "
+#~ "force attacks against the password."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "**Communicating the OnionShare address 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 ""
+
+#~ msgid ""
+#~ "**Communicating the OnionShare address might"
+#~ " not be anonymous.** Extra precautions "
+#~ "must be taken to ensure the "
+#~ "OnionShare address is communicated "
+#~ "anonymously. A new email or chat "
+#~ "account, only accessed over Tor, can "
+#~ "be used to share the address. This"
+#~ " isn't necessary unless anonymity is "
+#~ "a goal."
+#~ msgstr ""
+