onionshare/docs/source/locale/zh_CN/LC_MESSAGES/security.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Micah Lee, et al.
# This file is distributed under the same license as the OnionShare package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: OnionShare 2.3\n"
"Report-Msgid-Bugs-To: onionshare-dev@lists.riseup.net\n"
"POT-Creation-Date: 2020-12-13 15:48-0800\n"
"PO-Revision-Date: 2023-04-15 05:52+0000\n"
"Last-Translator: jxt <chihsun.tsai@gmail.com>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: zh_CN\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Weblate 4.17-dev\n"
"Generated-By: Babel 2.9.0\n"

#: ../../source/security.rst:2
msgid "Security Design"
msgstr "安全设计"

#: ../../source/security.rst:4
msgid "Read :ref:`how_it_works` first to get a handle on how OnionShare works."
msgstr "先阅读:ref:`how_it_works` 来了解基础的 OnionShare 运作原理。"

#: ../../source/security.rst:6
msgid "Like all software, OnionShare may contain bugs or vulnerabilities."
msgstr "一如所有应用程序，OnionShare 不免有错误或弱点。"

#: ../../source/security.rst:9
msgid "What OnionShare protects against"
msgstr "OnionShare 可保护的部份"

#: ../../source/security.rst:11
msgid ""
"**Third parties don't have access to anything that happens in OnionShare.** "
"Using OnionShare means hosting services directly on your computer. When "
"sharing files with OnionShare, they are not uploaded to any server. If you "
"make an OnionShare chat room, your computer acts as a server for that too. "
"This avoids the traditional model of having to trust the computers of others."
msgstr ""

#: ../../source/security.rst:13 ../../source/security.rst:17
msgid ""
"**Network eavesdroppers can't spy on anything that happens in OnionShare in "
"transit.** The connection between the Tor onion service and Tor Browser is "
"end-to-end encrypted. This means network attackers can't eavesdrop on "
"anything except encrypted Tor traffic. Even if an eavesdropper is a "
"malicious rendezvous node used to connect the Tor Browser with OnionShare's "
"onion service, the traffic is encrypted using the onion service's private "
"key."
msgstr ""
"**网路窃听者无法侦察 OnionShare 传输中发生的情况。 ** Tor 洋葱服务与 Tor 浏览"
"器之间为端到端加密连接，所以攻击者除了加密的 Tor 流量外无法窃听任何东西，即便"
"攻击者利用 Tor 浏览器与 OnionShare 洋葱服务连接的恶意会合节点，其流量也有洋葱"
"服务私钥加密。"

#: ../../source/security.rst:15 ../../source/security.rst:23
msgid ""
"**Anonymity of OnionShare users are protected by Tor.** OnionShare and Tor "
"Browser protect the anonymity of the users. As long as the OnionShare user "
"anonymously communicates the OnionShare address with the Tor Browser users, "
"the Tor Browser users and eavesdroppers can't learn the identity of the "
"OnionShare user."
msgstr ""
"**Tor 可保护 OnionShare 匿名 。 ** OnionShare 与 Tor 浏览器保护使用者匿名，只"
"要利用 OnionShare 地址与 Tor 浏览器进行匿名通信，Tor 浏览器与窃听者都无法知"
"道 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."
msgstr ""

#: ../../source/security.rst:20 ../../source/security.rst:33
msgid "What OnionShare doesn't protect against"
msgstr "OnionShare 不能保护的部份"

#: ../../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."
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."
msgstr ""

#: ../../source/security.rst:11
msgid ""
"**Third parties don't have access to anything that happens in OnionShare.** "
"Using OnionShare means hosting services directly on your computer. When "
"sharing your files with OnionShare, they are not uploaded to any third-party "
"server. If you make an OnionShare chat room, your computer acts as a server "
"for that too. This avoids the traditional model of having to trust the "
"computers of others."
msgstr ""

#: ../../source/security.rst:28
msgid ""
"**If an attacker learns about the onion service, they still can't access "
"anything.** Prior attacks against the Tor network to enumerate onion "
"services allowed attackers to discover private ``.onion`` addresses. To "
"access an OnionShare service from its address, the private key used for "
"client authentication must be guessed (unless the service is already made "
"public by turning off the private key -- see :ref:`turn_off_private_key`)."
msgstr ""

#: ../../source/security.rst:35
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 e-mail message "
"monitored by an attacker), an eavesdropper can tell that OnionShare is being "
"used. Eavesdroppers can access services that are still up by loading their "
"addresses and/or lost key in the Tor Browser. Avoid this by communicating "
"the address securely, via encrypted text message (probably with disappearing "
"messages enabled), encrypted e-mail, or in person. This isn't necessary when "
"using OnionShare for something that isn't secret."
msgstr ""

#: ../../source/security.rst:42
msgid ""
"**Communicating the OnionShare address and private key might not be "
"anonymous.** Extra precaution must be taken to ensure the OnionShare address "
"is communicated anonymously. A new e-mail or chat account, only accessed "
"over Tor, can be used to share the address. This isn't necessary unless "
"anonymity is a goal."
msgstr ""