onionshare/docs/source/locale/ko/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>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: OnionShare 2.5\n"
"Report-Msgid-Bugs-To: onionshare-dev@lists.riseup.net\n"
"POT-Creation-Date: 2022-01-17 10:28-0800\n"
"PO-Revision-Date: 2022-10-19 10:07+0000\n"
"Last-Translator: 이정희 <daemul72@gmail.com>\n"
"Language-Team: none\n"
"Language: ko\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.14.2-dev\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 ""
"OnionShare가 어떻게 작동하는지 알아보려면 먼저 :ref:`how_it_works`를 읽어보세"
"요."

#: ../../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 onion 서비스와 Tor 브라우저 간의 연결은 종단 간 암호화됩니다. 이"
"것은 네트워크 공격자가 암호화된 Tor 트래픽을 제외한 어떤 것도 도청할 수 없음"
"을 의미합니다. 도청자가 Tor 브라우저와 OnionShare의 onion 서비스를 연결하는 "
"데 사용되는 악의적인 접선 노드일지라도 트래픽은 onion 서비스의 개인 키를 사용"
"하여 암호화됩니다."

#: ../../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 ""
"**OnionShare 사용자의 익명성은 Tor에 의해 보호됩니다.** OnionShare 및 Tor 브"
"라우저는 사용자의 익명성을 보호합니다. OnionShare 사용자가 Tor 브라우저 사용"
"자와 익명으로 OnionShare 주소를 통신하는 한, 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, 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 ../../source/security.rst:33
msgid "What OnionShare doesn't protect against"
msgstr "OnionShare가 보호하지 않는 것"

#: ../../source/security.rst:22
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 "
"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 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 ""

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