onionshare/docs/source/locale/ru/LC_MESSAGES/security.po
2022-07-04 17:17:45 -04:00

381 lines
18 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# 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: 2022-07-04 17:16-0400\n"
"PO-Revision-Date: 2021-09-25 12:36+0000\n"
"Last-Translator: Alexander Tarasenko <alexound.login@gmail.com>\n"
"Language: ru\n"
"Language-Team: ru <LL@li.org>\n"
"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && "
"n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.10.3\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 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: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 ""
"**Наблюдающие за сетью не видят yичего из того, что происходит внтури "
"OnionShare в процессе передачи данных.** При создании соединения между "
"сервисом Tor onion и Tor Browser используется сквозное шифрование. Это "
"значит, что нападающий на сеть не видит ничего кроме зашифрованного "
"траффика сети Tor. Даже если злоумышленник завладеет промежуточным узлом "
"Tor, весь проходящий через него поток данных зашифрован при помощи "
"секретного ключа onion сервиса."
#: ../../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 Browser защищают анонимность пользователей. До тех пор, "
"пока пользователь OnionShare анонимно передаёт адрес сервиса OnionShare "
"пользователям Tor Browser, третьи лица не могут узнать личность "
"пользователя OnionShare."
#: ../../source/security.rst:28
#, fuzzy
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 ""
"**Даже если нападающий узнает о существовании сервиса OnionShare, доступ "
его содержимому полностью исключён**. Предыдущие атаки на сеть Tor "
"чтобы могли раскрыть секретные адреса ``.onion``. Если в результате атаки"
" будет раскрыт секретный адрес OnionShare, для доступа понадобится также "
"секретный ключ для аутентификации пользователя (кроме тех случаев, когда "
"сервис запущен как публичный -- подробнее :ref:`turn_off_private_key`)."
#: ../../source/security.rst:33
msgid "What OnionShare doesn't protect against"
msgstr "Против чего OnionShare не защищает"
#: ../../source/security.rst:35
#, fuzzy
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 ""
"**Передача адреса сервиса OnionShare и секретно ключа может быть "
"небезопасной.** Ответственность за передачу адреса сервиса OnionShare "
"возлагается на пользователя OnionShare. Если адрес передан небезопасным "
"способом (например через электронную почту, находящуюся под наблюдением) "
"злоумышленник может узнать, что используется OnionShare. Если "
"зломушленник введёт адрес сервиса OnionShare, пока сервис ещё активен, то"
" он может получить доступ к к нему. Чтобы избежать этого, передача адреса"
" должна осуществляться безопасным способом, например при помощи "
"зашифрованных сообщений (и, возможно, включённым режимом 'исчезающие "
"сообщения'), зашифрованной электронной почты или при личной встрече. Это "
"необязательно в случае, если OnionShare используется для передачи данных "
"не обладающих секретностью."
#: ../../source/security.rst:42
#, fuzzy
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 ""
"**Передача адреса OnionShare и секретного ключа может быть не "
"анонимной.** Дополнительные меры предосторожности должны быть предприняты"
" чтобы убедиться в анонимой передаче. Например, при помощи отдельной "
"учётной записи электронной почты или чата, доступ к которым "
"осуществляется только через сеть Tor. Это необязательно, если анонимность"
" передачи данных не является целью."
#~ msgid ""
#~ "**Third parties don't have access to "
#~ "anything that happens in OnionShare.** "
#~ "When you use OnionShare, you host "
#~ "services directly on your computer. For"
#~ " example, when you share files with"
#~ " OnionShare, you don't upload these "
#~ "files to any server, and when you"
#~ " start an OnionShare chat room, your"
#~ " computer is the chat room server "
#~ "itself. Traditional ways of sharing "
#~ "files or setting up websites and "
#~ "chat rooms require trusting a service"
#~ " with access to your data."
#~ msgstr ""
#~ msgid ""
#~ "**Network eavesdroppers can't spy on "
#~ "anything that happens in OnionShare in"
#~ " transit.** Because connections between Tor"
#~ " onion services and Tor Browser are"
#~ " end-to-end encrypted, no network "
#~ "attackers can eavesdrop on what happens"
#~ " in an OnionShare service. If the "
#~ "eavesdropper is positioned on the "
#~ "OnionShare user's end, the Tor Browser"
#~ " user's end, or is a malicious "
#~ "Tor node, they will only see Tor"
#~ " traffic. If the eavesdropper is a"
#~ " malicious rendezvous node used to "
#~ "connect Tor Browser with OnionShare's "
#~ "onion service, the traffic will be "
#~ "encrypted using the onion service key."
#~ msgstr ""
#~ msgid ""
#~ "**If an attacker learns about the "
#~ "onion service, they still can't access"
#~ " anything.** There have been attacks "
#~ "against the Tor network that can "
#~ "enumerate onion services. Even if "
#~ "someone discovers the .onion address of"
#~ " an OnionShare onion service, they "
#~ "can't access it without also knowing "
#~ "the service's random password (unless, "
#~ "of course, the OnionShare users chooses"
#~ " to disable the password and make "
#~ "it public). The password is generated"
#~ " by choosing two random words from"
#~ " a list of 6800 words, meaning "
#~ "there are 6800^2, or about 46 "
#~ "million possible password. But they can"
#~ " only make 20 wrong guesses before"
#~ " OnionShare stops the server, preventing"
#~ " brute force attacks against the "
#~ "password."
#~ msgstr ""
#~ msgid ""
#~ "**Communicating the OnionShare address might"
#~ " not be secure.** The OnionShare user"
#~ " is responsible for securely communicating"
#~ " the OnionShare address with people. "
#~ "If they send it insecurely (such "
#~ "as through an email message, and "
#~ "their email is being monitored by "
#~ "an attacker), the eavesdropper will "
#~ "learn that they're using OnionShare. If"
#~ " the attacker loads the address in"
#~ " Tor Browser before the legitimate "
#~ "recipient gets to it, they can "
#~ "access the service. If this risk "
#~ "fits the user's threat model, they "
#~ "must find a more secure way to "
#~ "communicate the address, such as in "
#~ "an encrypted email, chat, or voice "
#~ "call. This isn't necessary in cases "
#~ "where OnionShare is being used for "
#~ "something that isn't secret."
#~ msgstr ""
#~ msgid ""
#~ "**Communicating the OnionShare address might"
#~ " not be anonymous.** While OnionShare "
#~ "and Tor Browser allow for anonymity, "
#~ "if the user wishes to remain "
#~ "anonymous they must take extra steps "
#~ "to ensure this while communicating the"
#~ " OnionShare address. For example, they "
#~ "might need to use Tor to create"
#~ " a new anonymous email or chat "
#~ "account, and only access it over "
#~ "Tor, to use for sharing the "
#~ "address. This isn't necessary in cases"
#~ " where there's no need to protect "
#~ "anonymity, such as co-workers who "
#~ "know each other sharing work documents."
#~ 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^2, 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 anonymous.** Extra steps 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 ""
#~ "**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 ""
#~ "**Если злоумышленник узнаёт об onion "
#~ "сервисе, он всё равно не сможет "
#~ "получить доступ к каким либо данным.\""
#~ " ** В прошлом атака на сеть Tor"
#~ " позволяла нападающему узнать секретный "
#~ "адрес сервиса onion. Сейчас, если во "
#~ "время нападения на сеть становится "
#~ "известен секретный адрес OnionShare, пароль"
#~ " не позволит получить к нему доступ"
#~ " (кроме тех случаев, когда пользователь "
#~ "OnionShare отключит использование пароля и "
#~ "сделает сервис публичным). Пароль создаётся"
#~ " при помощи выбора двух случайных "
#~ "слов из списка длиной в 6800 слов,"
#~ " общее количество возможных комбинаций в"
#~ " таком случае составляет около 46 "
#~ "миллионов паролей. Всего 20 попыток "
#~ "ввести неверный пароль приведут к тому,"
#~ " что OnionShare остановит сервис и "
#~ "предотвратит возможность 'brute-force' атаки."
#~ 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,"
#~ " but not the private key used "
#~ "for Client Authentication, they will be"
#~ " prevented from accessing it (unless "
#~ "the OnionShare user chooses to turn "
#~ "off the private key and make it"
#~ " 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 ""
#~ "**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 ""
#~ "**Третьи лица не имеют доступа к "
#~ "каким бы то нибыло внутренним процессам"
#~ " OnionShare.** Использование OnionShare "
#~ "подразумевает размещение сервисов непосредственно"
#~ " на компьютере пользователя. Во время "
#~ "раздачи файлов при помощи OnionShare они"
#~ " не загружаются на какой-либо сервер. "
#~ "При использовании OnionShare в качестве "
#~ "чата, компьютер пользователя вытупает "
#~ "одновременно сервером. Таким образом "
#~ "исключается традиционная модель, при которой"
#~ " необходимо доверять компьютерам других "
#~ "пользователей."