remove obsolete strings, and some line wrapping

This commit is contained in:
emma peel 2023-05-31 13:54:10 +00:00
parent 22c035cf43
commit ac9e08eb91
471 changed files with 32637 additions and 66582 deletions

View file

@ -28,8 +28,8 @@ msgstr ""
#: ../../source/advanced.rst:9
msgid ""
"Closing OnionShare tabs you host destroys them, preventing reuse. "
"Persistently hosted websites are available on the same address even if "
"the computer they are shared from is rebooted."
"Persistently hosted websites are available on the same address even if the "
"computer they are shared from is rebooted."
msgstr ""
#: ../../source/advanced.rst:12
@ -40,16 +40,15 @@ msgstr ""
#: ../../source/advanced.rst:16
msgid ""
"When opening OnionShare, your saved tabs from the prior session will "
"start opened. Each service then can be started manually, and will be "
"available on the same OnionShare address and be protected by the same "
"private key."
"When opening OnionShare, your saved tabs from the prior session will start "
"opened. Each service then can be started manually, and will be available on "
"the same OnionShare address and be protected by the same private key."
msgstr ""
#: ../../source/advanced.rst:19
msgid ""
"If you save a tab, a copy of its onion service secret key is stored on "
"your computer."
"If you save a tab, a copy of its onion service secret key is stored on your "
"computer."
msgstr ""
#: ../../source/advanced.rst:24
@ -58,23 +57,23 @@ msgstr ""
#: ../../source/advanced.rst:26
msgid ""
"By default, all OnionShare services are protected with a private key, "
"which Tor calls \"client authentication\"."
"By default, all OnionShare services are protected with a private key, which "
"Tor calls \"client authentication\"."
msgstr ""
#: ../../source/advanced.rst:28
msgid ""
"The Tor Browser will ask you to enter your private key when you load an "
"OnionShare service. If you want allow the public to use your service, "
"it's better to disable the private key altogether."
"OnionShare service. If you want allow the public to use your service, it's "
"better to disable the private key altogether."
msgstr ""
#: ../../source/advanced.rst:31
msgid ""
"To turn off the private key for any tab, check the \"This is a public "
"OnionShare service (disables private key)\" box before starting the "
"server. Then the server will be public and a private key is not needed to"
" load it in the Tor Browser."
"OnionShare service (disables private key)\" box before starting the server. "
"Then the server will be public and a private key is not needed to load it in "
"the Tor Browser."
msgstr ""
#: ../../source/advanced.rst:37
@ -83,15 +82,15 @@ msgstr ""
#: ../../source/advanced.rst:39
msgid ""
"When people load OnionShare services in the Tor Browser they see the "
"default title for each type of service. For example, the default title "
"for chat services is \"OnionShare Chat\"."
"When people load OnionShare services in the Tor Browser they see the default "
"title for each type of service. For example, the default title for chat "
"services is \"OnionShare Chat\"."
msgstr ""
#: ../../source/advanced.rst:42
msgid ""
"If you edit the \"Custom title\" setting before starting a server you can"
" change it."
"If you edit the \"Custom title\" setting before starting a server you can "
"change it."
msgstr ""
#: ../../source/advanced.rst:45
@ -100,26 +99,26 @@ msgstr ""
#: ../../source/advanced.rst:47
msgid ""
"OnionShare supports scheduling exactly when a service should start and "
"stop. Before starting a server, click \"Show advanced settings\" in its "
"tab and then check the boxes next to either \"Start onion service at "
"scheduled time\", \"Stop onion service at scheduled time\", or both, and "
"set the respective desired dates and times."
"OnionShare supports scheduling exactly when a service should start and stop. "
"Before starting a server, click \"Show advanced settings\" in its tab and "
"then check the boxes next to either \"Start onion service at scheduled time"
"\", \"Stop onion service at scheduled time\", or both, and set the "
"respective desired dates and times."
msgstr ""
#: ../../source/advanced.rst:51
msgid ""
"Services scheduled to start in the future display a countdown timer when "
"when the \"Start sharing\" button is clicked. Services scheduled to stop "
"in the future display a countdown timer when started."
"when the \"Start sharing\" button is clicked. Services scheduled to stop in "
"the future display a countdown timer when started."
msgstr ""
#: ../../source/advanced.rst:54
msgid ""
"**Scheduling an OnionShare service to automatically start can be used as "
"a dead man's switch**. This means your service is made public at a given "
"time in the future if you are not there to prevent it. If nothing happens"
" to you, you can cancel the service before it's scheduled to start."
"**Scheduling an OnionShare service to automatically start can be used as a "
"dead man's switch**. This means your service is made public at a given time "
"in the future if you are not there to prevent it. If nothing happens to you, "
"you can cancel the service before it's scheduled to start."
msgstr ""
#: ../../source/advanced.rst:60
@ -141,8 +140,7 @@ msgstr ""
#: ../../source/advanced.rst:72
msgid ""
"You can install just the command-line version of OnionShare using "
"``pip3``::"
"You can install just the command-line version of OnionShare using ``pip3``::"
msgstr ""
#: ../../source/advanced.rst:76
@ -157,16 +155,15 @@ msgstr ""
#: ../../source/advanced.rst:82
msgid ""
"Info about installing it on different operating systems can be found in "
"the `CLI README file "
"<https://github.com/onionshare/onionshare/blob/develop/cli/README.md>`_ "
"in the Git repository."
"Info about installing it on different operating systems can be found in the "
"`CLI README file <https://github.com/onionshare/onionshare/blob/develop/cli/"
"README.md>`_ in the Git repository."
msgstr ""
#: ../../source/advanced.rst:84
msgid ""
"If you installed OnionShare using the Snap package, you can also just run"
" ``onionshare.cli`` to access the command-line interface version."
"If you installed OnionShare using the Snap package, you can also just run "
"``onionshare.cli`` to access the command-line interface version."
msgstr ""
#: ../../source/advanced.rst:87
@ -174,7 +171,8 @@ msgid "Usage"
msgstr ""
#: ../../source/advanced.rst:89
msgid "Browse the command-line documentation by running ``onionshare --help``::"
msgid ""
"Browse the command-line documentation by running ``onionshare --help``::"
msgstr ""
#: ../../source/advanced.rst:151
@ -190,491 +188,3 @@ msgstr ""
#: ../../source/advanced.rst:158
msgid "And from the main mode chooser screen::"
msgstr ""
#~ msgid "Make a symbolic link to the OnionShare command line binary line this::"
#~ msgstr ""
#~ msgid "Advanced usage"
#~ msgstr ""
#~ msgid "Save tabs"
#~ msgstr ""
#~ msgid ""
#~ "By default, everything in OnionShare is"
#~ " temporary. As soon as you close "
#~ "an OnionShare tab its address no "
#~ "longer exists and can't be used "
#~ "again. But sometimes you might want "
#~ "an OnionShare service to be persistent."
#~ " For example, this would be useful"
#~ " if you want to host a website"
#~ " that can keep the same URL "
#~ "even if you reboot your computer."
#~ msgstr ""
#~ msgid ""
#~ "When you quit OnionShare and then "
#~ "open it again, your saved tabs "
#~ "will start out open. You'll have "
#~ "to manually start each service, but "
#~ "when you do they will start with"
#~ " the same OnionShare address, and "
#~ "with the same password."
#~ msgstr ""
#~ msgid "Disable passwords"
#~ msgstr ""
#~ msgid ""
#~ "By default, all OnionShare services are"
#~ " protected with the username `onionshare`"
#~ " and a randomly-generated password. "
#~ "If someone makes 20 wrong guesses "
#~ "of the password, your onion service "
#~ "is automatically stopped to prevent a"
#~ " brute force attack against the "
#~ "OnionShare service."
#~ msgstr ""
#~ msgid ""
#~ "But sometimes you might want your "
#~ "OnionShare service to be accessible to"
#~ " the public. For example, if you "
#~ "want to set up an OnionShare "
#~ "receive service so the public can "
#~ "securely and anonymously send you files."
#~ " In this case, it's better to "
#~ "disable the password altogether. If you"
#~ " don't do this, someone can force "
#~ "your server to stop just by making"
#~ " 20 wrong guesses of your password,"
#~ " even if they know the correct "
#~ "password."
#~ msgstr ""
#~ msgid ""
#~ "To disable the password for any "
#~ "tab, just check the \"Don't use a"
#~ " password\" box before starting the "
#~ "server. Then the server will be "
#~ "public and won't have a password."
#~ msgstr ""
#~ msgid "Scheduled times"
#~ msgstr ""
#~ msgid ""
#~ "OnionShare supports scheduling exactly when"
#~ " a service should start and stop. "
#~ "Before starting server, click \"Show "
#~ "advanced settings\" in its tab and "
#~ "then check the boxes next to "
#~ "either \"Start onion service at "
#~ "scheduled time\", \"Stop onion service "
#~ "at scheduled time\", or both, and "
#~ "set the desired dates and times."
#~ msgstr ""
#~ msgid ""
#~ "If you scheduled a service to "
#~ "start in the future, when you "
#~ "click the start button you will "
#~ "see a timer counting down until it"
#~ " will start. If you scheduled it "
#~ "to stop in the future, after it's"
#~ " started you will see a timer "
#~ "counting down to when it will stop"
#~ " automatically."
#~ msgstr ""
#~ msgid ""
#~ "**Scheduling an OnionShare service to "
#~ "automatically stop can be useful to "
#~ "limit exposure**, like if you want "
#~ "to share secret documents while making"
#~ " sure they're not available on the"
#~ " internet for more than a few "
#~ "days."
#~ msgstr ""
#~ msgid "Command line interface"
#~ msgstr ""
#~ msgid ""
#~ "In addition to its graphical interface,"
#~ " OnionShare has a command line "
#~ "interface."
#~ msgstr ""
#~ msgid "Linux"
#~ msgstr ""
#~ msgid ""
#~ "If you installed OnionShare using the"
#~ " Flatpak package, unfortunately the command"
#~ " line interface isn't supported."
#~ msgstr ""
#~ msgid ""
#~ "If you installed OnionShare using an "
#~ "operating system package, you can just"
#~ " run ``onionshare`` from the terminal."
#~ msgstr ""
#~ msgid "macOS"
#~ msgstr ""
#~ msgid "Make a symbolic link to the OnionShare command line binary like this::"
#~ msgstr ""
#~ msgid "Now you can run ``onionshare`` from the terminal."
#~ msgstr ""
#~ msgid "Windows"
#~ msgstr ""
#~ msgid "The command line interface isn't supported in Windows."
#~ msgstr ""
#~ msgid ""
#~ "If you really want to use it "
#~ "anyway, you can set up a Windows"
#~ " development environment (see "
#~ ":ref:`starting_development`) and then run this"
#~ " in a command prompt::"
#~ msgstr ""
#~ msgid ""
#~ "You can see command line documentation"
#~ " by running ``onionshare --help``::"
#~ msgstr ""
#~ msgid "Legacy addresses"
#~ msgstr ""
#~ msgid ""
#~ "But it still has support for v2"
#~ " onion addresses, the old type of "
#~ "onion addresses that have 16 characters,"
#~ " for example::"
#~ msgstr ""
#~ msgid ""
#~ "OnionShare calls v2 onion addresses "
#~ "\"legacy addresses\". v3 onion addresses "
#~ "are more secure, and using legacy "
#~ "addresses is not recommended."
#~ msgstr ""
#~ msgid ""
#~ "To use legacy addresses, before starting"
#~ " a server click \"Show advanced "
#~ "settings\" in its tab and check "
#~ "the \"Use a legacy address (v2 "
#~ "onion service, not recommended)\" box. "
#~ "In legacy mode you can optionally "
#~ "enable Tor client authentication. Once "
#~ "you start a server in legacy mode"
#~ " you cannot remove legacy mode in "
#~ "that tab. Instead you must start a"
#~ " separate service in a separate tab."
#~ msgstr ""
#~ msgid ""
#~ "Tor Project plans to `completely "
#~ "deprecate v2 onion services "
#~ "<https://blog.torproject.org/v2-deprecation-timeline>`_ on"
#~ " October 15, 2021, and legacy onion"
#~ " services will soon be removed from"
#~ " OnionShare as well."
#~ msgstr ""
#~ msgid ""
#~ "When you quit OnionShare and then "
#~ "open it again, your saved tabs "
#~ "will start opened. You'll have to "
#~ "manually start each service, but when"
#~ " you do they will start with "
#~ "the same OnionShare address and "
#~ "password."
#~ msgstr ""
#~ msgid "Turn Off Passwords"
#~ msgstr ""
#~ msgid ""
#~ "By default, all OnionShare services are"
#~ " protected with the username ``onionshare``"
#~ " and a randomly-generated password. "
#~ "If someone takes 20 wrong guesses "
#~ "at the password, your onion service "
#~ "is automatically stopped to prevent a"
#~ " brute force attack against the "
#~ "OnionShare service."
#~ msgstr ""
#~ msgid ""
#~ "Sometimes you might want your OnionShare"
#~ " service to be accessible to the "
#~ "public, like if you want to set"
#~ " up an OnionShare receive service so"
#~ " the public can securely and "
#~ "anonymously send you files. In this "
#~ "case, it's better to disable the "
#~ "password altogether. If you don't do "
#~ "this, someone can force your server "
#~ "to stop just by making 20 wrong"
#~ " guesses of your password, even if"
#~ " they know the correct password."
#~ msgstr ""
#~ msgid ""
#~ "To turn off the password for any"
#~ " tab, just check the \"Don't use "
#~ "a password\" box before starting the "
#~ "server. Then the server will be "
#~ "public and won't have a password."
#~ msgstr ""
#~ msgid "Legacy Addresses"
#~ msgstr ""
#~ msgid ""
#~ "OnionShare uses v3 Tor onion services"
#~ " by default. These are modern onion"
#~ " addresses that have 56 characters, "
#~ "for example::"
#~ msgstr ""
#~ msgid ""
#~ "OnionShare still has support for v2 "
#~ "onion addresses, the old type of "
#~ "onion addresses that have 16 characters,"
#~ " for example::"
#~ msgstr ""
#~ msgid ""
#~ "OnionShare calls v2 onion addresses "
#~ "\"legacy addresses\", and they are not"
#~ " recommended, as v3 onion addresses "
#~ "are more secure."
#~ msgstr ""
#~ msgid ""
#~ "To use legacy addresses, before starting"
#~ " a server click \"Show advanced "
#~ "settings\" from its tab and check "
#~ "the \"Use a legacy address (v2 "
#~ "onion service, not recommended)\" box. "
#~ "In legacy mode you can optionally "
#~ "turn on Tor client authentication. Once"
#~ " you start a server in legacy "
#~ "mode you cannot remove legacy mode "
#~ "in that tab. Instead you must "
#~ "start a separate service in a "
#~ "separate tab."
#~ msgstr ""
#~ msgid ""
#~ "Tor Project plans to `completely "
#~ "deprecate v2 onion services "
#~ "<https://blog.torproject.org/v2-deprecation-timeline>`_ on"
#~ " October 15, 2021, and legacy onion"
#~ " services will be removed from "
#~ "OnionShare before then."
#~ msgstr ""
#~ msgid ""
#~ "By default, all OnionShare services are"
#~ " protected with a private key, which"
#~ " Tor calls Client Authentication."
#~ msgstr ""
#~ msgid ""
#~ "**Scheduling an OnionShare service to "
#~ "automatically stop can be useful to "
#~ "limit exposure**, like if you want "
#~ "to share secret documents while making"
#~ " sure they're not available on the"
#~ " Internet for more than a few "
#~ "days."
#~ msgstr ""
#~ msgid ""
#~ "For more information, see the `CLI "
#~ "readme file "
#~ "<https://github.com/onionshare/onionshare/blob/develop/cli/README.md>`_"
#~ " in the git repository."
#~ msgstr ""
#~ msgid ""
#~ "Everything in OnionShare is temporary by"
#~ " default. If you close an OnionShare"
#~ " tab, its address no longer exists"
#~ " and it can't be used again. "
#~ "Sometimes you might want an OnionShare"
#~ " service to be persistent. This is"
#~ " useful if you want to host a"
#~ " website available from the same "
#~ "OnionShare address even if you reboot"
#~ " your computer."
#~ msgstr ""
#~ msgid ""
#~ "To make any tab persistent, check "
#~ "the \"Save this tab, and automatically"
#~ " open it when I open OnionShare\" "
#~ "box before starting the server. When "
#~ "a tab is saved a purple pin "
#~ "icon appears to the left of its"
#~ " server status."
#~ msgstr ""
#~ msgid ""
#~ "When you quit OnionShare and then "
#~ "open it again, your saved tabs "
#~ "will start opened. You'll have to "
#~ "manually start each service, but when"
#~ " you do they will start with "
#~ "the same OnionShare address and private"
#~ " key."
#~ msgstr ""
#~ msgid ""
#~ "If you save a tab, a copy of"
#~ " that tab's onion service secret key"
#~ " will be stored on your computer "
#~ "with your OnionShare settings."
#~ msgstr ""
#~ msgid ""
#~ "When browsing to an OnionShare service"
#~ " in Tor Browser, Tor Browser will "
#~ "prompt for the private key to be"
#~ " entered."
#~ msgstr ""
#~ msgid ""
#~ "Sometimes you might want your OnionShare"
#~ " service to be accessible to the "
#~ "public, like if you want to set"
#~ " up an OnionShare receive service so"
#~ " the public can securely and "
#~ "anonymously send you files. In this "
#~ "case, it's better to disable the "
#~ "private key altogether."
#~ msgstr ""
#~ msgid ""
#~ "To turn off the private key for"
#~ " any tab, check the \"This is a"
#~ " public OnionShare service (disables "
#~ "private key)\" box before starting the"
#~ " server. Then the server will be "
#~ "public and won't need a private "
#~ "key to view in Tor Browser."
#~ msgstr ""
#~ msgid ""
#~ "By default, when people load an "
#~ "OnionShare service in Tor Browser they"
#~ " see the default title for the "
#~ "type of service. For example, the "
#~ "default title of a chat service is"
#~ " \"OnionShare Chat\"."
#~ msgstr ""
#~ msgid ""
#~ "If you want to choose a custom "
#~ "title, set the \"Custom title\" setting"
#~ " before starting a server."
#~ msgstr ""
#~ msgid ""
#~ "If you scheduled a service to "
#~ "start in the future, when you "
#~ "click the \"Start sharing\" button you"
#~ " will see a timer counting down "
#~ "until it starts. If you scheduled "
#~ "it to stop in the future, after"
#~ " it's started you will see a "
#~ "timer counting down to when it "
#~ "will stop automatically."
#~ msgstr ""
#~ msgid ""
#~ "**Scheduling an OnionShare service to "
#~ "automatically start can be used as "
#~ "a dead man's switch**, where your "
#~ "service will be made public at a"
#~ " given time in the future if "
#~ "anything happens to you. If nothing "
#~ "happens to you, you can cancel the"
#~ " service before it's scheduled to "
#~ "start."
#~ msgstr ""
#~ msgid ""
#~ "For information about installing it on"
#~ " different operating systems, see the "
#~ "`CLI readme file "
#~ "<https://github.com/onionshare/onionshare/blob/develop/cli/README.md>`_"
#~ " in the git repository."
#~ msgstr ""
#~ msgid ""
#~ "If you installed OnionShare using the"
#~ " Linux Snapcraft package, you can "
#~ "also just run ``onionshare.cli`` to "
#~ "access the command-line interface "
#~ "version."
#~ msgstr ""
#~ msgid ""
#~ "You can browse the command-line "
#~ "documentation by running ``onionshare "
#~ "--help``::"
#~ msgstr ""
#~ msgid ""
#~ "The OnionShare desktop application contains"
#~ " some keyboard shortcuts, for convenience"
#~ " and accessibility."
#~ msgstr ""
#~ msgid "Ctrl T - New Tab Ctrl X - Closes current tab"
#~ msgstr ""
#~ msgid "And from the main mode chooser screen:"
#~ msgstr ""
#~ msgid ""
#~ "Ctrl S - Share mode Ctrl R -"
#~ " Receive mode Ctrl W - Website "
#~ "mode Ctrl C - Chat mode Ctrl "
#~ "H - Settings tab"
#~ msgstr ""
#~ msgid ""
#~ "Everything in OnionShare is temporary by"
#~ " default. When OnionShare tabs are "
#~ "closed, addresses no longer exist and"
#~ " can't be used again. Your OnionShare"
#~ " service can also be persistent. If"
#~ " you host a website, persistence "
#~ "means it will be available on the"
#~ " same OnionShare address even if you"
#~ " reboot your computer."
#~ msgstr ""
#~ msgid ""
#~ "To make any tab persistent, check "
#~ "the \"Save this tab, and automatically"
#~ " open it when I open OnionShare\" "
#~ "box before starting your server. A "
#~ "purple pin icon appears to the "
#~ "left of its server status to tell"
#~ " you the tab is saved."
#~ msgstr ""

View file

@ -23,22 +23,22 @@ msgstr ""
#: ../../source/connecting.rst:4
msgid ""
"When OnionShare starts, it will present a screen asking you to connect to"
" the Tor network."
"When OnionShare starts, it will present a screen asking you to connect to "
"the Tor network."
msgstr ""
#: ../../source/connecting.rst:8
msgid ""
"You have several choices. You can click Connect to Tor to begin the "
"connection process. If there are no problems with your network, including"
" any attempts to block your access to the Tor network, this should "
"hopefully work the first time."
"connection process. If there are no problems with your network, including "
"any attempts to block your access to the Tor network, this should hopefully "
"work the first time."
msgstr ""
#: ../../source/connecting.rst:10
msgid ""
"If you want to manually configure Bridges or other Tor settings before "
"you connect, you can click 'Network Settings'."
"If you want to manually configure Bridges or other Tor settings before you "
"connect, you can click 'Network Settings'."
msgstr ""
#: ../../source/connecting.rst:13
@ -47,15 +47,15 @@ msgstr ""
#: ../../source/connecting.rst:15
msgid ""
"When OnionShare fails to connect to Tor, it might be because Tor is "
"censored in your country."
"When OnionShare fails to connect to Tor, it might be because Tor is censored "
"in your country."
msgstr ""
#: ../../source/connecting.rst:17
msgid ""
"If this occurs, a screen will be displayed that will offer you to either "
"'Use a Bridge' (automatically choosing one for you), or 'Try Again "
"without a Bridge'."
"'Use a Bridge' (automatically choosing one for you), or 'Try Again without a "
"Bridge'."
msgstr ""
#: ../../source/connecting.rst:22
@ -64,18 +64,18 @@ msgstr ""
#: ../../source/connecting.rst:24
msgid ""
"Bridges are a way to connect to the Tor network via intermediate services"
" that are hopefully not blocked by your network provider (whereas normal "
"Bridges are a way to connect to the Tor network via intermediate services "
"that are hopefully not blocked by your network provider (whereas normal "
"connections might be)."
msgstr ""
#: ../../source/connecting.rst:26
msgid ""
"Clicking 'Use a Bridge' will temporarily use the `Meek "
"<https://gitlab.torproject.org/legacy/trac/-/wikis/doc/meek/>`_ domain-"
"fronting proxy to make a non-Tor connection from your computer to the Tor"
" Project's Censorship Circumvention API. The use of the Meek proxy is to "
"hide the fact that you are trying to find a way to connect to Tor."
"Clicking 'Use a Bridge' will temporarily use the `Meek <https://gitlab."
"torproject.org/legacy/trac/-/wikis/doc/meek/>`_ domain-fronting proxy to "
"make a non-Tor connection from your computer to the Tor Project's Censorship "
"Circumvention API. The use of the Meek proxy is to hide the fact that you "
"are trying to find a way to connect to Tor."
msgstr ""
#: ../../source/connecting.rst:28
@ -101,45 +101,43 @@ msgstr ""
msgid ""
"If you choose to manually select a country, OnionShare will still make a "
"request to the Censorship Circumvention API, but will tell the API the "
"country code. The API will then try to fetch bridges for that country "
"that you specified."
"country code. The API will then try to fetch bridges for that country that "
"you specified."
msgstr ""
#: ../../source/connecting.rst:38
msgid ""
"If it finds any such bridges, OnionShare will try to reconnect to Tor "
"using those bridges."
"If it finds any such bridges, OnionShare will try to reconnect to Tor using "
"those bridges."
msgstr ""
#: ../../source/connecting.rst:40
msgid ""
"If the API does not find any bridges for your location, OnionShare will "
"ask the API for 'fallback' options. At the time of writing, this is "
"likely to be the obfs4 built-in bridges."
"If the API does not find any bridges for your location, OnionShare will ask "
"the API for 'fallback' options. At the time of writing, this is likely to be "
"the obfs4 built-in bridges."
msgstr ""
#: ../../source/connecting.rst:42
msgid ""
"OnionShare will also attempt to use the obfs4 built-in bridges if for "
"some reason it could not connect to the API itself, or the API returned "
"an error."
"OnionShare will also attempt to use the obfs4 built-in bridges if for some "
"reason it could not connect to the API itself, or the API returned an error."
msgstr ""
#: ../../source/connecting.rst:44
msgid ""
"It's important to note that the requests to the Censorship Circumvention "
"API do not go over the Tor Network (because if you could connect to Tor "
"already, you wouldn't need to connect to the API)."
"It's important to note that the requests to the Censorship Circumvention API "
"do not go over the Tor Network (because if you could connect to Tor already, "
"you wouldn't need to connect to the API)."
msgstr ""
#: ../../source/connecting.rst:46
msgid ""
"Even though it is hard for an adversary to discover where the Meek "
"request is going, this may still be risky for some users. Therefore, it "
"is an opt-in feature. The use of Meek and non-torified network requests "
"are limited only to making one or two requests to the Censorship "
"Circumvention API. Then Meek is stopped, and all further network requests"
" happen over the Tor network."
"Even though it is hard for an adversary to discover where the Meek request "
"is going, this may still be risky for some users. Therefore, it is an opt-in "
"feature. The use of Meek and non-torified network requests are limited only "
"to making one or two requests to the Censorship Circumvention API. Then Meek "
"is stopped, and all further network requests happen over the Tor network."
msgstr ""
#: ../../source/connecting.rst:49
@ -149,8 +147,8 @@ msgstr ""
#: ../../source/connecting.rst:51
msgid ""
"Clicking 'Try again without a Bridge' will retry the normal OnionShare "
"connection attempt to Tor. It won't talk to the Tor Censorship "
"Circumvention API or use Meek."
"connection attempt to Tor. It won't talk to the Tor Censorship Circumvention "
"API or use Meek."
msgstr ""
#: ../../source/connecting.rst:54
@ -159,133 +157,14 @@ msgstr ""
#: ../../source/connecting.rst:56
msgid ""
"You can toggle on the switch 'Connect to Tor automatically' before "
"clicking 'Connect to Tor'. This means that next time OnionShare starts, "
"it will automatically connect with its Tor connection settings from the "
"last session, instead of presenting you with the connection options."
"You can toggle on the switch 'Connect to Tor automatically' before clicking "
"'Connect to Tor'. This means that next time OnionShare starts, it will "
"automatically connect with its Tor connection settings from the last "
"session, instead of presenting you with the connection options."
msgstr ""
#: ../../source/connecting.rst:58
msgid ""
"If the connection fails, you can still try bridges or reconfigure Tor via"
" the 'Network Settings'."
"If the connection fails, you can still try bridges or reconfigure Tor via "
"the 'Network Settings'."
msgstr ""
#~ msgid ""
#~ "If you want to use Bridges to "
#~ "connect to Tor, you can click "
#~ "Network Settings to configure your type"
#~ " of Tor connection or any bridge "
#~ "settings. You can read more about "
#~ "the Tor Settings screen at "
#~ ":ref:`tor_settings`"
#~ msgstr ""
#~ msgid ""
#~ "When OnionShare tries to connect to "
#~ "Tor, and experiences a problem, it "
#~ "may be because Tor is censored in"
#~ " your country."
#~ msgstr ""
#~ msgid ""
#~ "If this occurs, a screen will be"
#~ " displayed that will offer you to "
#~ "either 'Use a Bridge' (automatically "
#~ "choosing one for you), or 'Try "
#~ "Again without a Bridge'. You can "
#~ "also click 'Network Settings' to "
#~ "configure other custom bridges or for"
#~ " other ways to use Tor."
#~ msgstr ""
#~ msgid ""
#~ "You can choose either 'Automatically "
#~ "determine my country from my IP "
#~ "address' or 'Manually select my "
#~ "country', before clicking 'Use a "
#~ "Bridge'."
#~ msgstr ""
#~ msgid ""
#~ "If you choose to automatically determine"
#~ " your country, clicking 'Use a "
#~ "Bridge' will temporarily use the `Meek"
#~ " <https://gitlab.torproject.org/legacy/trac/-/wikis/doc/meek/>`_"
#~ " domain-fronting proxy to make a "
#~ "non-Tor connection from your computer"
#~ " to the Tor Project's Censorship "
#~ "Circumvention API. The use of the "
#~ "Meek proxy is to defeat any "
#~ "censorship attempt against your computer's "
#~ "ability to reach the API itself."
#~ msgstr ""
#~ msgid ""
#~ "The Censorship Circumvention API will "
#~ "consider your IP address (yes, your "
#~ "real IP address) to determine what "
#~ "country you might reside in."
#~ msgstr ""
#~ msgid ""
#~ "If you choose to manually select a"
#~ " country, OnionShare will still make "
#~ "a Meek-driven request to the "
#~ "Censorship Circumvention API, but will "
#~ "tell the API the country code. The"
#~ " API will then try to fetch "
#~ "bridges for that country that you "
#~ "specified."
#~ msgstr ""
#~ msgid ""
#~ "If the API does not find any "
#~ "bridges for your location, OnionShare "
#~ "will ask the API for 'fallback' "
#~ "options. At the time of writing, "
#~ "this is likely to be the OBFS4 "
#~ "built-in bridges."
#~ msgstr ""
#~ msgid ""
#~ "It's important to note that the "
#~ "requests to the Censorship Circumvention "
#~ "API do not go over the Tor "
#~ "Network (if you could use Tor "
#~ "already, you wouldn't need to talk "
#~ "to the API!). Even though it is"
#~ " hard for an adversary to discover"
#~ " where the Meek request is going, "
#~ "this may still be risky for some"
#~ " users. Therefore, it is an opt-"
#~ "in feature. The use of Meek and"
#~ " non-torified network requests are "
#~ "limited only to making one or two"
#~ " requests to the Censorship Circumvention"
#~ " API. Then Meek is stopped, and "
#~ "all further network requests happen over"
#~ " the Tor network."
#~ msgstr ""
#~ msgid ""
#~ "Clicking 'Try again without a Bridge'"
#~ " will simply retry the normal "
#~ "OnionShare connection attempt to Tor. It"
#~ " won't talk to the Tor Censorship "
#~ "Circumvention API or use Meek."
#~ msgstr ""
#~ msgid ""
#~ "You can toggle on the switch "
#~ "'Connect to Tor automatically' before "
#~ "clicking 'Connect to Tor'. This means"
#~ " that next time OnionShare starts, it"
#~ " will automatically connect instead of "
#~ "presenting you with the configuration "
#~ "options."
#~ msgstr ""
#~ msgid "If the connection fails, you can still try bridges."
#~ msgstr ""

View file

@ -27,21 +27,19 @@ msgstr ""
#: ../../source/develop.rst:9
msgid ""
"OnionShare has an open Keybase team to discuss the project, ask "
"questions, share ideas and designs, and making plans for future "
"development. (It's also an easy way to send end-to-end encrypted direct "
"messages to others in the OnionShare community, like OnionShare "
"addresses.) To use Keybase, download the `Keybase app "
"<https://keybase.io/download>`_, make an account, and `join this team "
"<https://keybase.io/team/onionshare>`_. Within the app, go to \"Teams\", "
"click \"Join a Team\", and type \"onionshare\"."
"OnionShare has an open Keybase team to discuss the project, ask questions, "
"share ideas and designs, and making plans for future development. (It's also "
"an easy way to send end-to-end encrypted direct messages to others in the "
"OnionShare community, like OnionShare addresses.) To use Keybase, download "
"the `Keybase app <https://keybase.io/download>`_, make an account, and `join "
"this team <https://keybase.io/team/onionshare>`_. Within the app, go to "
"\"Teams\", click \"Join a Team\", and type \"onionshare\"."
msgstr ""
#: ../../source/develop.rst:12
msgid ""
"OnionShare also has a `mailing list "
"<https://lists.riseup.net/www/subscribe/onionshare-dev>`_ for developers "
"and and designers to discuss the project."
"OnionShare also has a `mailing list <https://lists.riseup.net/www/subscribe/"
"onionshare-dev>`_ for developers and and designers to discuss the project."
msgstr ""
#: ../../source/develop.rst:15
@ -50,24 +48,23 @@ msgstr ""
#: ../../source/develop.rst:17
msgid ""
"OnionShare source code is to be found in this Git repository: "
"https://github.com/onionshare/onionshare"
"OnionShare source code is to be found in this Git repository: https://github."
"com/onionshare/onionshare"
msgstr ""
#: ../../source/develop.rst:19
msgid ""
"If you'd like to contribute code to OnionShare, it helps to join the "
"Keybase team and ask questions about what you're thinking of working on. "
"You should also review all of the `open issues "
"<https://github.com/onionshare/onionshare/issues>`_ on GitHub to see if "
"there are any you'd like to tackle."
"If you'd like to contribute code to OnionShare, it helps to join the Keybase "
"team and ask questions about what you're thinking of working on. You should "
"also review all of the `open issues <https://github.com/onionshare/"
"onionshare/issues>`_ on GitHub to see if there are any you'd like to tackle."
msgstr ""
#: ../../source/develop.rst:22
msgid ""
"When you're ready to contribute code, open a pull request in the GitHub "
"repository and one of the project maintainers will review it and possibly"
" ask questions, request changes, reject it, or merge it into the project."
"repository and one of the project maintainers will review it and possibly "
"ask questions, request changes, reject it, or merge it into the project."
msgstr ""
#: ../../source/develop.rst:27
@ -76,12 +73,11 @@ msgstr ""
#: ../../source/develop.rst:29
msgid ""
"OnionShare is developed in Python. To get started, clone the Git "
"repository at https://github.com/onionshare/onionshare/ and then consult "
"the ``cli/README.md`` file to learn how to set up your development "
"environment for the command-line version, and the ``desktop/README.md`` "
"file to learn how to set up your development environment for the "
"graphical version."
"OnionShare is developed in Python. To get started, clone the Git repository "
"at https://github.com/onionshare/onionshare/ and then consult the ``cli/"
"README.md`` file to learn how to set up your development environment for the "
"command-line version, and the ``desktop/README.md`` file to learn how to set "
"up your development environment for the graphical version."
msgstr ""
#: ../../source/develop.rst:32
@ -101,9 +97,9 @@ msgstr ""
#: ../../source/develop.rst:40
msgid ""
"When developing, it's convenient to run OnionShare from a terminal and "
"add the ``--verbose`` (or ``-v``) flag to the command. This prints a lot "
"of helpful messages to the terminal, such as when certain objects are "
"When developing, it's convenient to run OnionShare from a terminal and add "
"the ``--verbose`` (or ``-v``) flag to the command. This prints a lot of "
"helpful messages to the terminal, such as when certain objects are "
"initialized, when events occur (like buttons clicked, settings saved or "
"reloaded), and other debug info. For example::"
msgstr ""
@ -116,9 +112,9 @@ msgstr ""
#: ../../source/develop.rst:121
msgid ""
"This can be useful when learning the chain of events that occur when "
"using OnionShare, or the value of certain variables before and after they"
" are manipulated."
"This can be useful when learning the chain of events that occur when using "
"OnionShare, or the value of certain variables before and after they are "
"manipulated."
msgstr ""
#: ../../source/develop.rst:124
@ -134,9 +130,9 @@ msgstr ""
#: ../../source/develop.rst:165
msgid ""
"In this case, you load the URL ``http://127.0.0.1:17641`` in a normal "
"web-browser like Firefox, instead of using the Tor Browser. The private "
"key is not actually needed in local-only mode, so you can ignore it."
"In this case, you load the URL ``http://127.0.0.1:17641`` in a normal web-"
"browser like Firefox, instead of using the Tor Browser. The private key is "
"not actually needed in local-only mode, so you can ignore it."
msgstr ""
#: ../../source/develop.rst:168
@ -146,14 +142,14 @@ msgstr ""
#: ../../source/develop.rst:170
msgid ""
"Help make OnionShare easier to use and more familiar and welcoming for "
"people by translating it on `Hosted Weblate "
"<https://hosted.weblate.org/projects/onionshare/>`_. Always keep the "
"\"OnionShare\" in latin letters, and use \"OnionShare (localname)\" if "
"needed."
"people by translating it on `Hosted Weblate <https://hosted.weblate.org/"
"projects/onionshare/>`_. Always keep the \"OnionShare\" in latin letters, "
"and use \"OnionShare (localname)\" if needed."
msgstr ""
#: ../../source/develop.rst:172
msgid "To help translate, make a Hosted Weblate account and start contributing."
msgid ""
"To help translate, make a Hosted Weblate account and start contributing."
msgstr ""
#: ../../source/develop.rst:175
@ -162,16 +158,16 @@ msgstr ""
#: ../../source/develop.rst:177
msgid ""
"Sometimes the original English strings are wrong, or don't match between "
"the application and the documentation."
"Sometimes the original English strings are wrong, or don't match between the "
"application and the documentation."
msgstr ""
#: ../../source/develop.rst:179
msgid ""
"File source string improvements by adding @kingu to your Weblate comment,"
" or open a GitHub issue or pull request. The latter ensures all upstream "
"developers see the suggestion, and can potentially modify the string via "
"the usual code review processes."
"File source string improvements by adding @kingu to your Weblate comment, or "
"open a GitHub issue or pull request. The latter ensures all upstream "
"developers see the suggestion, and can potentially modify the string via the "
"usual code review processes."
msgstr ""
#: ../../source/develop.rst:183
@ -180,271 +176,7 @@ msgstr ""
#: ../../source/develop.rst:184
msgid ""
"Here is the current translation status. If you want start a translation "
"in a language not yet started, please write to the mailing list: "
"onionshare-dev@lists.riseup.net"
"Here is the current translation status. If you want start a translation in a "
"language not yet started, please write to the mailing list: onionshare-"
"dev@lists.riseup.net"
msgstr ""
#~ msgid ""
#~ "OnionShare is developed in Python. To"
#~ " get started, you should close the"
#~ " git repository at "
#~ "https://github.com/micahflee/onionshare/ and then "
#~ "consult the ``BUILD.md`` file."
#~ msgstr ""
#~ msgid ""
#~ "OnionShare has an open Keybase team "
#~ "that we use to discuss the "
#~ "project, including asking questions, sharing"
#~ " ideas and designs, and making plans"
#~ " for future development. (It's also "
#~ "an easy way to send end-to-"
#~ "end encrypted direct messages to others"
#~ " in the OnionShare community, like "
#~ "OnionShare addresses.) To use Keybase, "
#~ "you need to download the `Keybase "
#~ "app <https://keybase.io/download>`_, make an "
#~ "account, and `join this team "
#~ "<https://keybase.io/team/onionshare>`_. Within the "
#~ "app, go to Teams, click \"Join a"
#~ " Team\", and type \"onionshare\"."
#~ msgstr ""
#~ msgid "Contributing code"
#~ msgstr ""
#~ msgid ""
#~ "OnionShare source code is in this "
#~ "git repository: https://github.com/micahflee/onionshare"
#~ msgstr ""
#~ msgid ""
#~ "If you'd like to contribute code "
#~ "to OnionShare, it helps to join "
#~ "the Keybase team and ask questions "
#~ "about what you're thinking of working"
#~ " on. You should also review all "
#~ "of the `open issues "
#~ "<https://github.com/micahflee/onionshare/issues>`_ on "
#~ "GitHub to see if there are any "
#~ "that you'd like to develop."
#~ msgstr ""
#~ msgid ""
#~ "When you're ready to contribute code,"
#~ " open a pull request in the "
#~ "GitHub repository and one of the "
#~ "project maintainers will review it and"
#~ " possible ask questions, request changes,"
#~ " reject it, or merge it into "
#~ "the project."
#~ msgstr ""
#~ msgid "Starting development"
#~ msgstr ""
#~ msgid ""
#~ "OnionShare is developed in Python. To"
#~ " get started, you should clone the"
#~ " git repository at "
#~ "https://github.com/micahflee/onionshare/ and then "
#~ "consult the ``BUILD.md`` file."
#~ msgstr ""
#~ msgid "That file contains the technical instructions and commands necessary:"
#~ msgstr ""
#~ msgid "Install dependencies for your platform"
#~ msgstr ""
#~ msgid "Run OnionShare from the source tree, without building a package"
#~ msgstr ""
#~ msgid "Building packages"
#~ msgstr ""
#~ msgid "Making a release of OnionShare"
#~ msgstr ""
#~ msgid ""
#~ "When developing, it's convenient to run"
#~ " OnionShare from a terminal and add"
#~ " the ``--verbose`` (or ``-v``) flag "
#~ "to the command. This will print a"
#~ " lot of helpful messages to the "
#~ "terminal such as when certain objects"
#~ " are initialized, when events occur "
#~ "(like buttons clicked, settings saved or"
#~ " reloaded), and other debug information."
#~ " For example::"
#~ msgstr ""
#~ msgid ""
#~ "This can be useful when learning "
#~ "the chain of events that occur "
#~ "when using the application or the "
#~ "value of certain variables before and"
#~ " after they are manipulated."
#~ msgstr ""
#~ msgid "Local only"
#~ msgstr ""
#~ msgid ""
#~ "In this case, you load the URL "
#~ "``http://onionshare:eject-snack@127.0.0.1:17614`` in "
#~ "a normal web browser like Firefox, "
#~ "instead of using Tor Browser."
#~ msgstr ""
#~ msgid "Debugging in Windows"
#~ msgstr ""
#~ msgid ""
#~ "If you want to obtain debug output"
#~ " from the ``onionshare-gui.exe`` in "
#~ "Windows, you will need to edit "
#~ "``install\\pyinstaller.spec`` and change "
#~ "``console=False`` to ``console=True``."
#~ msgstr ""
#~ msgid ""
#~ "Then rebuild the EXE with "
#~ "``install\\build_exe.bat`` (you may need to"
#~ " comment out the ``signtool`` commands "
#~ "in the ``build_exe.bat`` and the "
#~ "``onionshare.nsi`` files, as per the "
#~ "``BUILD.md`` instructions)."
#~ msgstr ""
#~ msgid ""
#~ "After this, you can run ``onionshare-"
#~ "gui.exe -v`` from a command prompt "
#~ "to see the debug output."
#~ msgstr ""
#~ msgid "Contributing translations"
#~ msgstr ""
#~ msgid ""
#~ "Most of the OnionShare is translatable."
#~ " You can help make it easier to"
#~ " use and more familiar and welcoming"
#~ " for people around the globe. The "
#~ "Localization Lab has some `documentation "
#~ "about translating OnionShare "
#~ "<https://wiki.localizationlab.org/index.php/OnionShare>`_."
#~ msgstr ""
#~ msgid ""
#~ "OnionShare uses Weblate to keep track"
#~ " of translations. You can view the"
#~ " OnionShare project here: "
#~ "https://hosted.weblate.org/projects/onionshare/"
#~ msgstr ""
#~ msgid ""
#~ "To help translate, make a Hosted "
#~ "Weblate account and start contributing "
#~ "to that project."
#~ msgstr ""
#~ msgid "Suggestions for original English strings"
#~ msgstr ""
#~ msgid ""
#~ "Sometimes the original English strings "
#~ "could be improved, making them easier"
#~ " to translate into other languages."
#~ msgstr ""
#~ msgid ""
#~ "If you have suggestions for a "
#~ "better English string, please open a "
#~ "GitHub issue rather than commenting in"
#~ " Weblate. This ensures the upstream "
#~ "developers will definitely see the "
#~ "suggestion, and can potentially modify "
#~ "the string via the usual code "
#~ "review processes."
#~ msgstr ""
#~ msgid "Status of translations"
#~ msgstr ""
#~ msgid ""
#~ "Here is the current translation status."
#~ " If you want start a translation "
#~ "in a language not to be found "
#~ "here, please write us to the "
#~ "mailing list: onionshare-dev@lists.riseup.net"
#~ msgstr ""
#~ msgid "Translate the .desktop file"
#~ msgstr ""
#~ msgid "You can also translate the ``install/onionshare.desktop`` file."
#~ msgstr ""
#~ msgid ""
#~ "Duplicate the line that begins with "
#~ "``Comment=``. Add the language code to"
#~ " the new line so it becomes "
#~ "``Comment[lang]=`` (lang should be your "
#~ "language). You can see what language "
#~ "codes are used for translation by "
#~ "looking at the ``share/locale/*.json`` "
#~ "filenames::"
#~ msgstr ""
#~ msgid "Do the same for other untranslated lines."
#~ msgstr ""
#~ msgid ""
#~ "OnionShare source code is to be "
#~ "found in this Git repository: "
#~ "https://github.com/micahflee/onionshare"
#~ msgstr ""
#~ msgid ""
#~ "If you'd like to contribute code "
#~ "to OnionShare, it helps to join "
#~ "the Keybase team and ask questions "
#~ "about what you're thinking of working"
#~ " on. You should also review all "
#~ "of the `open issues "
#~ "<https://github.com/micahflee/onionshare/issues>`_ on "
#~ "GitHub to see if there are any "
#~ "you'd like to tackle."
#~ msgstr ""
#~ msgid ""
#~ "OnionShare is developed in Python. To"
#~ " get started, clone the Git "
#~ "repository at https://github.com/micahflee/onionshare/ "
#~ "and then consult the ``cli/README.md`` "
#~ "file to learn how to set up "
#~ "your development environment for the "
#~ "command-line version, and the "
#~ "``desktop/README.md`` file to learn how "
#~ "to set up your development environment"
#~ " for the graphical version."
#~ msgstr ""
#~ msgid ""
#~ "In this case, you load the URL "
#~ "``http://onionshare:train-system@127.0.0.1:17635`` in "
#~ "a normal web-browser like Firefox, "
#~ "instead of using the Tor Browser."
#~ msgstr ""
#~ msgid ""
#~ "In this case, you load the URL "
#~ "``http://127.0.0.1:17621`` in a normal web-"
#~ "browser like Firefox, instead of using"
#~ " the Tor Browser. The Private key "
#~ "is not actually needed in local-"
#~ "only mode, so you can ignore it."
#~ msgstr ""

File diff suppressed because it is too large Load diff

View file

@ -27,8 +27,8 @@ msgstr ""
#: ../../source/help.rst:7
msgid ""
"You will find instructions on how to use OnionShare. Look through all of "
"the sections first to see if anything answers your questions."
"You will find instructions on how to use OnionShare. Look through all of the "
"sections first to see if anything answers your questions."
msgstr ""
#: ../../source/help.rst:10
@ -37,10 +37,10 @@ msgstr ""
#: ../../source/help.rst:12
msgid ""
"If it isn't on the website, please check the `GitHub issues "
"<https://github.com/onionshare/onionshare/issues>`_. It's possible "
"someone else has encountered the same problem and either raised it with "
"the developers, or maybe even posted a solution."
"If it isn't on the website, please check the `GitHub issues <https://github."
"com/onionshare/onionshare/issues>`_. It's possible someone else has "
"encountered the same problem and either raised it with the developers, or "
"maybe even posted a solution."
msgstr ""
#: ../../source/help.rst:15
@ -49,11 +49,10 @@ msgstr ""
#: ../../source/help.rst:17
msgid ""
"If you are unable to find a solution, or wish to ask a question or "
"suggest a new feature, please `submit an issue "
"<https://github.com/onionshare/onionshare/issues/new>`_. This requires "
"`creating a GitHub account <https://help.github.com/articles/signing-up-"
"for-a-new-github-account/>`_."
"If you are unable to find a solution, or wish to ask a question or suggest a "
"new feature, please `submit an issue <https://github.com/onionshare/"
"onionshare/issues/new>`_. This requires `creating a GitHub account <https://"
"help.github.com/articles/signing-up-for-a-new-github-account/>`_."
msgstr ""
#: ../../source/help.rst:20
@ -62,80 +61,6 @@ msgstr ""
#: ../../source/help.rst:22
msgid ""
"See :ref:`collaborating` on how to join the Keybase team used to discuss "
"the project."
"See :ref:`collaborating` on how to join the Keybase team used to discuss the "
"project."
msgstr ""
#~ msgid "If you need help with OnionShare, please follow the instructions below."
#~ msgstr ""
#~ msgid "Read this website"
#~ msgstr ""
#~ msgid ""
#~ "This website is full of instructions "
#~ "on how to use OnionShare. Look "
#~ "through all of the sections first "
#~ "to see if it answers your "
#~ "questions."
#~ msgstr ""
#~ msgid "Check the GitHub issues"
#~ msgstr ""
#~ msgid ""
#~ "If you can't find a solution in"
#~ " this website, please check the "
#~ "`GitHub issues "
#~ "<https://github.com/micahflee/onionshare/issues>`_. It's "
#~ "possible that someone else has "
#~ "encountered the same problem and has "
#~ "either raised it with the developers,"
#~ " or maybe even posted a solution."
#~ msgstr ""
#~ msgid "Submit an issue yourself"
#~ msgstr ""
#~ msgid ""
#~ "If you can't find a solution to"
#~ " your problem, or you wish to "
#~ "ask a question or suggest a new"
#~ " feature, please `submit an issue "
#~ "<https://github.com/micahflee/onionshare/issues/new>`_. This "
#~ "requires `creating an GitHub account "
#~ "<https://help.github.com/articles/signing-up-for-a-new-"
#~ "github-account/>`_."
#~ msgstr ""
#~ msgid "Join our Keybase team"
#~ msgstr ""
#~ msgid ""
#~ "See :ref:`collaborating` for instructions on"
#~ " how to join our Keybase team "
#~ "that we use to discuss the "
#~ "project."
#~ msgstr ""
#~ msgid ""
#~ "If it isn't on the website, please"
#~ " check the `GitHub issues "
#~ "<https://github.com/micahflee/onionshare/issues>`_. It's "
#~ "possible someone else has encountered "
#~ "the same problem and either raised "
#~ "it with the developers, or maybe "
#~ "even posted a solution."
#~ msgstr ""
#~ msgid ""
#~ "If you are unable to find a "
#~ "solution, or wish to ask a "
#~ "question or suggest a new feature, "
#~ "please `submit an issue "
#~ "<https://github.com/micahflee/onionshare/issues/new>`_. This "
#~ "requires `creating a GitHub account "
#~ "<https://help.github.com/articles/signing-up-for-a-new-"
#~ "github-account/>`_."
#~ msgstr ""

View file

@ -26,4 +26,3 @@ msgid ""
"OnionShare is an open source tool that lets you securely and anonymously "
"share files, host websites, and chat with friends using the Tor network."
msgstr ""

View file

@ -35,32 +35,32 @@ 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."
"**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."
"**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 ""
#: ../../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."
"**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 ""
#: ../../source/security.rst:28
@ -69,9 +69,8 @@ msgid ""
"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`)."
"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:33
@ -80,350 +79,22 @@ 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."
"**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."
"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 ""
#~ msgid "Security design"
#~ msgstr ""
#~ msgid ""
#~ "First read :ref:`how_it_works` to understand"
#~ " the basics of how OnionShare works."
#~ msgstr ""
#~ 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 ""
#~ 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 ""
#~ 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 ""
#~ "**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 ""
#~ 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 ""
#~ 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 ""
#~ 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 ""
#~ 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 ""
#~ 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 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 ""

View file

@ -24,4 +24,3 @@ msgstr ""
#: ../../source/_templates/versions.html:18
msgid "Languages"
msgstr ""

View file

@ -23,32 +23,31 @@ msgstr ""
#: ../../source/tor.rst:4
msgid ""
"When OnionShare starts, it will show you a screen asking you to connect "
"to the Tor network."
"When OnionShare starts, it will show you a screen asking you to connect to "
"the Tor network."
msgstr ""
#: ../../source/tor.rst:8
msgid ""
"You can toggle on the switch \"Connect to Tor automatically\" before "
"clicking \"Connect to Tor\". This means that next time OnionShare starts,"
" it will automatically connect with its Tor connection settings from the "
"last session, instead of presenting you with the connection options. If "
"the connection fails, you can still try bridges or reconfigure Tor via "
"the \"Network Settings\" button."
"clicking \"Connect to Tor\". This means that next time OnionShare starts, it "
"will automatically connect with its Tor connection settings from the last "
"session, instead of presenting you with the connection options. If the "
"connection fails, you can still try bridges or reconfigure Tor via the "
"\"Network Settings\" button."
msgstr ""
#: ../../source/tor.rst:11
msgid ""
"You can click \"Connect to Tor\" to begin the connection process. If "
"there are no problems with your network, including any attempts to block "
"your access to the Tor network, this should hopefully work the first "
"time."
"You can click \"Connect to Tor\" to begin the connection process. If there "
"are no problems with your network, including any attempts to block your "
"access to the Tor network, this should hopefully work the first time."
msgstr ""
#: ../../source/tor.rst:13
msgid ""
"Or, if you want to manually configure Bridges or other Tor settings "
"before you connect, you can click \"Network Settings\"."
"Or, if you want to manually configure Bridges or other Tor settings before "
"you connect, you can click \"Network Settings\"."
msgstr ""
#: ../../source/tor.rst:16
@ -57,9 +56,8 @@ msgstr ""
#: ../../source/tor.rst:18
msgid ""
"When you click \"Connect to Tor\", if OnionShare fails to connect, it "
"might be because Tor is censored in your country or on your local "
"network."
"When you click \"Connect to Tor\", if OnionShare fails to connect, it might "
"be because Tor is censored in your country or on your local network."
msgstr ""
#: ../../source/tor.rst:20
@ -71,7 +69,8 @@ msgid "Try again without a bridge"
msgstr ""
#: ../../source/tor.rst:23
msgid "Automatically determine my country from my IP address for bridge settings"
msgid ""
"Automatically determine my country from my IP address for bridge settings"
msgstr ""
#: ../../source/tor.rst:24
@ -81,19 +80,17 @@ msgstr ""
#: ../../source/tor.rst:28
msgid ""
"If you choose the \"Try again without a bridge\" option, OnionShare will "
"retry connecting to Tor like normal, without attempting to bypass "
"censorship."
"retry connecting to Tor like normal, without attempting to bypass censorship."
msgstr ""
#: ../../source/tor.rst:30
msgid ""
"The other two options will attempt to automatically bypass censorship "
"using Tor bridges. If your network provider is blocking access to the Tor"
" network, you can hopefully still connect to a Tor bridge, which will "
"then connect you to the Tor network, circumventing the censorship. Both "
"of these options use the Tor Project's Censorship Circumvention API to "
"provide you with bridge settings that should work for you. OnionShare "
"will temporarily use the `Meek "
"The other two options will attempt to automatically bypass censorship using "
"Tor bridges. If your network provider is blocking access to the Tor network, "
"you can hopefully still connect to a Tor bridge, which will then connect you "
"to the Tor network, circumventing the censorship. Both of these options use "
"the Tor Project's Censorship Circumvention API to provide you with bridge "
"settings that should work for you. OnionShare will temporarily use the `Meek "
"<https://gitlab.torproject.org/legacy/trac/-/wikis/doc/meek/>`_ domain-"
"fronting proxy to make a non-Tor connection from your computer to Tor's "
"Censorship Circumvention API. The Meek proxy hides the fact that you are "
@ -102,10 +99,10 @@ msgstr ""
#: ../../source/tor.rst:36
msgid ""
"If you choose \"Automatically determine my country from my IP address for"
" bridge settings\", the Censorship Circumvention API will consider your "
"IP address (yes, your real IP address) to determine what country you "
"might reside in. Based on the country information, the API will try to "
"If you choose \"Automatically determine my country from my IP address for "
"bridge settings\", the Censorship Circumvention API will consider your IP "
"address (yes, your real IP address) to determine what country you might "
"reside in. Based on the country information, the API will try to "
"automatically find bridges that suit your location."
msgstr ""
@ -122,42 +119,41 @@ msgstr ""
#: ../../source/tor.rst:48
msgid ""
"If the Censorship Circumvention API finds bridges that it believes will "
"suit you, OnionShare will try to reconnect to Tor using those bridges. If"
" the API does not find any bridges for your location, OnionShare will ask"
" the API for \"fallback\" options, and then try to reconnect using those."
"If the Censorship Circumvention API finds bridges that it believes will suit "
"you, OnionShare will try to reconnect to Tor using those bridges. If the API "
"does not find any bridges for your location, OnionShare will ask the API for "
"\"fallback\" options, and then try to reconnect using those."
msgstr ""
#: ../../source/tor.rst:50
msgid ""
"If for some reason OnionShare fails to connect to the Censorship API "
"itself, or if the API returns an error message, OnionShare will attempt "
"to use the obfs4 built-in bridges."
"If for some reason OnionShare fails to connect to the Censorship API itself, "
"or if the API returns an error message, OnionShare will attempt to use the "
"obfs4 built-in bridges."
msgstr ""
#: ../../source/tor.rst:52
msgid ""
"It's important to note that the requests to the Censorship Circumvention "
"API do not go over the Tor network (because if you could connect to Tor "
"already, you wouldn't need to connect to the API)."
"It's important to note that the requests to the Censorship Circumvention API "
"do not go over the Tor network (because if you could connect to Tor already, "
"you wouldn't need to connect to the API)."
msgstr ""
#: ../../source/tor.rst:54
msgid ""
"Even though it's hard for an adversary to discover where the Meek request"
" is going, this may still be risky for some users. Therefore, it is an "
"opt-in feature. The use of Meek and non-torified network requests are "
"limited only to making one or two requests to the Censorship "
"Circumvention API. Then Meek is stopped, and all further network requests"
" happen over the Tor network."
"Even though it's hard for an adversary to discover where the Meek request is "
"going, this may still be risky for some users. Therefore, it is an opt-in "
"feature. The use of Meek and non-torified network requests are limited only "
"to making one or two requests to the Censorship Circumvention API. Then Meek "
"is stopped, and all further network requests happen over the Tor network."
msgstr ""
#: ../../source/tor.rst:56
msgid ""
"If you are uncomfortable with making a request that doesn't go over the "
"Tor network, you can click \"Network Settings\" (or the Settings icon in "
"the bottom right corner, followed by the Tor Settings tab in the screen "
"that appears), and manually configure bridges. After you save any bridge "
"If you are uncomfortable with making a request that doesn't go over the Tor "
"network, you can click \"Network Settings\" (or the Settings icon in the "
"bottom right corner, followed by the Tor Settings tab in the screen that "
"appears), and manually configure bridges. After you save any bridge "
"settings, OnionShare will try to reconnect using those bridges."
msgstr ""
@ -168,15 +164,14 @@ msgstr ""
#: ../../source/tor.rst:61
msgid ""
"You can get to the Tor settings by clicking \"Network Settings\" on the "
"welcome screen, or by clicking the \"⚙\" icon in the bottom-right corner "
"of the application, and then switch to the Tor Settings tab in the screen"
" that appears."
"welcome screen, or by clicking the \"⚙\" icon in the bottom-right corner of "
"the application, and then switch to the Tor Settings tab in the screen that "
"appears."
msgstr ""
#: ../../source/tor.rst:65
msgid ""
"Here are the different ways you can configure OnionShare to connect to "
"Tor:"
"Here are the different ways you can configure OnionShare to connect to Tor:"
msgstr ""
#: ../../source/tor.rst:68
@ -185,16 +180,16 @@ msgstr ""
#: ../../source/tor.rst:70
msgid ""
"This is the default, simplest and most reliable way that OnionShare "
"connects to Tor. For this reason, it's recommended for most users."
"This is the default, simplest and most reliable way that OnionShare connects "
"to Tor. For this reason, it's recommended for most users."
msgstr ""
#: ../../source/tor.rst:73
msgid ""
"When you open OnionShare, it launches an already configured ``tor`` "
"process in the background for OnionShare to use. It doesn't interfere "
"with other ``tor`` processes on your computer, so you can use the Tor "
"Browser or the system ``tor`` on their own."
"When you open OnionShare, it launches an already configured ``tor`` process "
"in the background for OnionShare to use. It doesn't interfere with other "
"``tor`` processes on your computer, so you can use the Tor Browser or the "
"system ``tor`` on their own."
msgstr ""
#: ../../source/tor.rst:76
@ -203,14 +198,14 @@ msgstr ""
#: ../../source/tor.rst:78
msgid ""
"To use a bridge, you must select \"Use the Tor version built into "
"OnionShare\" and check the \"Use a bridge\" checkbox."
"To use a bridge, you must select \"Use the Tor version built into OnionShare"
"\" and check the \"Use a bridge\" checkbox."
msgstr ""
#: ../../source/tor.rst:80
msgid ""
"Try using a built-in bridge first. Using `obfs4` or `snowflake` bridges "
"is recommended over using `meek-azure`."
"Try using a built-in bridge first. Using `obfs4` or `snowflake` bridges is "
"recommended over using `meek-azure`."
msgstr ""
#: ../../source/tor.rst:84
@ -233,10 +228,10 @@ msgstr ""
#: ../../source/tor.rst:93
msgid ""
"If you have `downloaded the Tor Browser <https://www.torproject.org>`_ "
"and don't want two ``tor`` processes running, you can use the ``tor`` "
"process from the Tor Browser. Keep in mind you need to keep Tor Browser "
"open in the background while you're using OnionShare for this to work."
"If you have `downloaded the Tor Browser <https://www.torproject.org>`_ and "
"don't want two ``tor`` processes running, you can use the ``tor`` process "
"from the Tor Browser. Keep in mind you need to keep Tor Browser open in the "
"background while you're using OnionShare for this to work."
msgstr ""
#: ../../source/tor.rst:97
@ -245,16 +240,16 @@ msgstr ""
#: ../../source/tor.rst:99
msgid ""
"This is fairly advanced. You'll need to know how edit plaintext files and"
" do stuff as an administrator."
"This is fairly advanced. You'll need to know how edit plaintext files and do "
"stuff as an administrator."
msgstr ""
#: ../../source/tor.rst:101
msgid ""
"Download the Tor Windows Expert Bundle `from "
"<https://www.torproject.org/download/tor/>`_. Extract the compressed file"
" and copy the extracted folder to ``C:\\Program Files (x86)\\`` Rename "
"the extracted folder with ``Data`` and ``Tor`` in it to ``tor-win32``."
"Download the Tor Windows Expert Bundle `from <https://www.torproject.org/"
"download/tor/>`_. Extract the compressed file and copy the extracted folder "
"to ``C:\\Program Files (x86)\\`` Rename the extracted folder with ``Data`` "
"and ``Tor`` in it to ``tor-win32``."
msgstr ""
#: ../../source/tor.rst:105
@ -268,24 +263,23 @@ msgstr ""
#: ../../source/tor.rst:112
msgid ""
"The hashed password output is displayed after some warnings (which you "
"can ignore). In the case of the above example, it is "
"The hashed password output is displayed after some warnings (which you can "
"ignore). In the case of the above example, it is "
"``16:00322E903D96DE986058BB9ABDA91E010D7A863768635AC38E213FDBEF``."
msgstr ""
#: ../../source/tor.rst:114
msgid ""
"Now create a new text file at ``C:\\Program Files (x86)\\tor-"
"win32\\torrc`` and put your hashed password output in it, replacing the "
"Now create a new text file at ``C:\\Program Files (x86)\\tor-win32\\torrc`` "
"and put your hashed password output in it, replacing the "
"``HashedControlPassword`` with the one you just generated::"
msgstr ""
#: ../../source/tor.rst:119
msgid ""
"In your administrator command prompt, install ``tor`` as a service using "
"the appropriate ``torrc`` file you just created (as described in "
"`<https://2019.www.torproject.org/docs/faq.html.en#NTService>`_). Like "
"this::"
"In your administrator command prompt, install ``tor`` as a service using the "
"appropriate ``torrc`` file you just created (as described in `<https://2019."
"www.torproject.org/docs/faq.html.en#NTService>`_). Like this::"
msgstr ""
#: ../../source/tor.rst:123
@ -294,13 +288,13 @@ msgstr ""
#: ../../source/tor.rst:125
msgid ""
"Open OnionShare, click the \"⚙\" icon in it, and switch to the Tor "
"Settings tab. Under \"How should OnionShare connect to Tor?\" choose "
"\"Connect using control port\", and set \"Control port\" to ``127.0.0.1``"
" and \"Port\" to ``9051``. Under \"Tor authentication settings\" choose "
"\"Password\" and set the password to the control port password you picked"
" above. Click the \"Test Connection to Tor\" button. If all goes well, "
"you should see \"Connected to the Tor controller\"."
"Open OnionShare, click the \"⚙\" icon in it, and switch to the Tor Settings "
"tab. Under \"How should OnionShare connect to Tor?\" choose \"Connect using "
"control port\", and set \"Control port\" to ``127.0.0.1`` and \"Port\" to "
"``9051``. Under \"Tor authentication settings\" choose \"Password\" and set "
"the password to the control port password you picked above. Click the \"Test "
"Connection to Tor\" button. If all goes well, you should see \"Connected to "
"the Tor controller\"."
msgstr ""
#: ../../source/tor.rst:134
@ -309,8 +303,8 @@ msgstr ""
#: ../../source/tor.rst:136
msgid ""
"First, install `Homebrew <https://brew.sh/>`_ if you don't already have "
"it, and then install Tor::"
"First, install `Homebrew <https://brew.sh/>`_ if you don't already have it, "
"and then install Tor::"
msgstr ""
#: ../../source/tor.rst:140
@ -323,12 +317,12 @@ msgstr ""
#: ../../source/tor.rst:151
msgid ""
"Open OnionShare, click the \"⚙\" icon in it, and switch to the Tor "
"Settings tab. Under \"How should OnionShare connect to Tor?\" choose "
"\"Connect using socket file\", and set the socket file to be "
"``/usr/local/var/run/tor/control.socket``. Under \"Tor authentication "
"settings\" choose \"No authentication, or cookie authentication\". Click "
"the \"Test Connection to Tor\" button."
"Open OnionShare, click the \"⚙\" icon in it, and switch to the Tor Settings "
"tab. Under \"How should OnionShare connect to Tor?\" choose \"Connect using "
"socket file\", and set the socket file to be ``/usr/local/var/run/tor/"
"control.socket``. Under \"Tor authentication settings\" choose \"No "
"authentication, or cookie authentication\". Click the \"Test Connection to "
"Tor\" button."
msgstr ""
#: ../../source/tor.rst:157 ../../source/tor.rst:177
@ -342,394 +336,29 @@ msgstr ""
#: ../../source/tor.rst:162
msgid ""
"First, install the ``tor`` package. If you're using Debian, Ubuntu, or a "
"similar Linux distro, It is recommended to use the Tor Project's "
"`official repository <https://support.torproject.org/apt/tor-deb-"
"repo/>`_."
"similar Linux distro, It is recommended to use the Tor Project's `official "
"repository <https://support.torproject.org/apt/tor-deb-repo/>`_."
msgstr ""
#: ../../source/tor.rst:164
msgid ""
"Next, add your user to the group that runs the ``tor`` process (in the "
"case of Debian and Ubuntu, ``debian-tor``) and configure OnionShare to "
"connect to your system ``tor``'s control socket file."
"Next, add your user to the group that runs the ``tor`` process (in the case "
"of Debian and Ubuntu, ``debian-tor``) and configure OnionShare to connect to "
"your system ``tor``'s control socket file."
msgstr ""
#: ../../source/tor.rst:166
msgid ""
"Add your user to the ``debian-tor`` group by running this command "
"(replace ``username`` with your actual username)::"
"Add your user to the ``debian-tor`` group by running this command (replace "
"``username`` with your actual username)::"
msgstr ""
#: ../../source/tor.rst:170
msgid ""
"Reboot your computer. After it boots up again, open OnionShare, click the"
" \"⚙\" icon in it, and switch to the Tor Settings tab. Under \"How should"
" OnionShare connect to Tor?\" choose \"Connect using socket file\". Set "
"the socket file to be ``/var/run/tor/control``. Under \"Tor "
"authentication settings\" choose \"No authentication, or cookie "
"authentication\". Click the \"Test Connection to Tor\" button."
"Reboot your computer. After it boots up again, open OnionShare, click the \"⚙"
"\" icon in it, and switch to the Tor Settings tab. Under \"How should "
"OnionShare connect to Tor?\" choose \"Connect using socket file\". Set the "
"socket file to be ``/var/run/tor/control``. Under \"Tor authentication "
"settings\" choose \"No authentication, or cookie authentication\". Click the "
"\"Test Connection to Tor\" button."
msgstr ""
#~ msgid "Using a system Tor in Mac OS X"
#~ msgstr ""
#~ msgid ""
#~ "There are several options for how "
#~ "OnionShare should connect to Tor. You"
#~ " can change them in Settings, which"
#~ " you can get to by clicking the"
#~ " gear icon in the bottom-right "
#~ "of the window."
#~ msgstr ""
#~ msgid "Use Tor that is bundled with OnionShare"
#~ msgstr ""
#~ msgid ""
#~ "This is the default way that "
#~ "OnionShare connects to Tor, and it's "
#~ "also the simplest and most reliable "
#~ "way. For this reason, it's recommended"
#~ " for most users."
#~ msgstr ""
#~ msgid ""
#~ "When you open OnionShare, it will "
#~ "launch a Tor process in the "
#~ "background that's configured specifically for"
#~ " OnionShare to use. This Tor process"
#~ " won't interfere with other Tor "
#~ "processes on your computer, so you're"
#~ " free to run Tor Browser or use"
#~ " a system Tor in the background."
#~ msgstr ""
#~ msgid "Attempt automatic configuration with Tor Browser"
#~ msgstr ""
#~ msgid ""
#~ "You can configure OnionShare to connect"
#~ " to the Tor that comes with Tor"
#~ " Browser. First, `download Tor Browser "
#~ "<https://www.torproject.org>`_ here if you "
#~ "don't already have it. With this "
#~ "setting selected, you need to keep "
#~ "Tor Browser open in the background "
#~ "while you're using OnionShare."
#~ msgstr ""
#~ msgid "Using a system Tor in Windows"
#~ msgstr ""
#~ msgid ""
#~ "Download the Tor Windows Expert Bundle,"
#~ " which you can get `from here "
#~ "<https://www.torproject.org/download/tor/>`_. Extract the"
#~ " zip file and copy the extracted "
#~ "folder to ``C:\\Program Files (x86)\\``, "
#~ "and rename the folder to ``tor-"
#~ "win32``, so that inside that folder "
#~ "is the ``Data`` and ``Tor`` folders."
#~ msgstr ""
#~ msgid ""
#~ "Make up a control port password. "
#~ "I'm going to use ``comprised stumble "
#~ "rummage work avenging construct volatile`` "
#~ "as my password. Now open a command"
#~ " prompt as an administrator, and use"
#~ " ``tor.exe --hash-password`` to generate"
#~ " a hash of your password. For "
#~ "example::"
#~ msgstr ""
#~ msgid ""
#~ "The hashed password output is displayed"
#~ " after some warnings (which you can"
#~ " ignore). In my case, it was "
#~ "``16:00322E903D96DE986058BB9ABDA91E010D7A863768635AC38E213FDBEF``."
#~ msgstr ""
#~ msgid ""
#~ "Now create a new text file at "
#~ "``C:\\Program Files (x86)\\tor-win32\\torrc`` "
#~ "and put this in it, replacing the"
#~ " ``HashedControlPassword`` with the one you"
#~ " just generated::"
#~ msgstr ""
#~ msgid ""
#~ "In your administrator command prompt, "
#~ "install tor as a service using the"
#~ " appropriate ``torrc`` file you just "
#~ "created (see `here "
#~ "<https://2019.www.torproject.org/docs/faq.html.en#NTService>`_ "
#~ "for more information on doing this). "
#~ "Like this::"
#~ msgstr ""
#~ msgid "You're now running a system Tor in Windows!"
#~ msgstr ""
#~ msgid ""
#~ "Open OnionShare. Click the Settings "
#~ "icon. Under \"How should OnionShare "
#~ "connect to Tor?\" choose \"Connect using"
#~ " control port\", and set the control"
#~ " port host to ``127.0.0.1`` and the"
#~ " port to ``9051``. Under \"Tor "
#~ "authentication options\" choose \"Password\" "
#~ "and set the password to your "
#~ "password, in my case ``comprised stumble"
#~ " rummage work avenging construct "
#~ "volatile``. Click the \"Test Settings\" "
#~ "button. If all goes well, you "
#~ "should see successfully connected to "
#~ "tor."
#~ msgstr ""
#~ msgid "Using a system Tor in macOS"
#~ msgstr ""
#~ msgid ""
#~ "First, install `Homebrew <http://brew.sh/>`_ "
#~ "if you don't already have it. "
#~ "Then, install Tor::"
#~ msgstr ""
#~ msgid ""
#~ "Open OnionShare. Click the Settings "
#~ "icon. Under \"How should OnionShare "
#~ "connect to Tor?\" choose \"Connect using"
#~ " socket file\", and set the socket"
#~ " file to be "
#~ "``/usr/local/var/run/tor/control.socket``. Under \"Tor "
#~ "authentication options\" choose \"No "
#~ "authentication, or cookie authentication\". "
#~ "Click the \"Test Settings\" button. If"
#~ " all goes well, you should see "
#~ "successfully connected to tor."
#~ msgstr ""
#~ msgid "Using a system Tor in Linux"
#~ msgstr ""
#~ msgid ""
#~ "First, install the tor package. If "
#~ "you're using Debian, Ubuntu, or a "
#~ "similar Linux distro, I recommend you"
#~ " use Tor Project's `official repository "
#~ "<https://2019.www.torproject.org/docs/debian.html.en>`_. For "
#~ "example, in Ubuntu 20.04::"
#~ msgstr ""
#~ msgid ""
#~ "Next, add your user to the group"
#~ " that runs the Tor process (in "
#~ "the case of Debian and Ubuntu, "
#~ "``debian-tor``) and configure OnionShare to"
#~ " connect to your system Tor's control"
#~ " socket file."
#~ msgstr ""
#~ msgid ""
#~ "Reboot your computer. After it boots "
#~ "up again, open OnionShare. Click the "
#~ "Settings icon. Under \"How should "
#~ "OnionShare connect to Tor?\" choose "
#~ "\"Connect using socket file\", and set"
#~ " the socket file to be "
#~ "``/var/run/tor/control``. Under \"Tor authentication"
#~ " options\" choose \"No authentication, or"
#~ " cookie authentication\". Click the \"Test"
#~ " Settings\" button. If all goes well,"
#~ " you should see successfully connect "
#~ "to Tor."
#~ msgstr ""
#~ msgid ""
#~ "If your access to the internet is"
#~ " censored, you can configure OnionShare "
#~ "to connect to the Tor network "
#~ "using `Tor bridges "
#~ "<https://2019.www.torproject.org/docs/bridges.html.en>`_. If "
#~ "OnionShare successfully connects to Tor, "
#~ "you don't need to use a bridge."
#~ msgstr ""
#~ msgid "To configure bridges, open OnionShare settings."
#~ msgstr ""
#~ msgid ""
#~ "You can use the built-in obfs4 "
#~ "pluggable transports, the built-in "
#~ "meek_lite (Azure) pluggable transports, or "
#~ "custom bridges, which you can obtain "
#~ "from Tor's `BridgeDB "
#~ "<https://bridges.torproject.org/>`_. If you need "
#~ "to use a bridge, you should try"
#~ " the built-in obfs4 ones first."
#~ msgstr ""
#~ msgid ""
#~ "Download the Tor Windows Expert Bundle"
#~ " `from <https://www.torproject.org/download/tor/>`_. "
#~ "Extract the ZIP file and copy the"
#~ " extracted folder to ``C:\\Program Files"
#~ " (x86)\\`` Rename the extracted folder "
#~ "with ``Data`` and ``Tor`` in it to"
#~ " ``tor-win32``."
#~ msgstr ""
#~ msgid ""
#~ "Open OnionShare and click the \"⚙\" "
#~ "icon in it. Under \"How should "
#~ "OnionShare connect to Tor?\" choose "
#~ "\"Connect using control port\", and set"
#~ " \"Control port\" to ``127.0.0.1`` and "
#~ "\"Port\" to ``9051``. Under \"Tor "
#~ "authentication settings\" choose \"Password\" "
#~ "and set the password to the "
#~ "control port password you picked above"
#~ " Click the \"Test Connection to Tor\""
#~ " button. If all goes well, you "
#~ "should see \"Connected to the Tor "
#~ "controller\"."
#~ msgstr ""
#~ msgid ""
#~ "First, install `Homebrew <https://brew.sh/>`_ "
#~ "if you don't already have it. "
#~ "Then, install Tor::"
#~ msgstr ""
#~ msgid ""
#~ "If your access to the Internet is"
#~ " censored, you can configure OnionShare "
#~ "to connect to the Tor network "
#~ "using `Tor bridges "
#~ "<https://2019.www.torproject.org/docs/bridges.html.en>`_. If "
#~ "OnionShare connects to Tor without one,"
#~ " you don't need to use a "
#~ "bridge."
#~ msgstr ""
#~ msgid ""
#~ "Pick a way to connect OnionShare "
#~ "to Tor by clicking the \"⚙\" icon"
#~ " in the bottom right of the "
#~ "OnionShare window to get to its "
#~ "settings."
#~ msgstr ""
#~ msgid "Use the ``tor`` bundled with OnionShare"
#~ msgstr ""
#~ msgid "Using Tor bridges"
#~ msgstr ""
#~ msgid ""
#~ "If your access to the internet is"
#~ " censored, you can configure OnionShare "
#~ "to connect to the Tor network "
#~ "using `Tor bridges "
#~ "<https://2019.www.torproject.org/docs/bridges.html.en>`_. If "
#~ "OnionShare connects to Tor without one,"
#~ " you don't need to use a "
#~ "bridge."
#~ msgstr ""
#~ msgid "To configure bridges, click the \"⚙\" icon in OnionShare."
#~ msgstr ""
#~ msgid ""
#~ "You can use the built-in obfs4 "
#~ "pluggable transports, the built-in "
#~ "meek_lite (Azure) pluggable transports, or "
#~ "custom bridges, which you can obtain "
#~ "from Tor's `BridgeDB "
#~ "<https://bridges.torproject.org/>`_. If you need "
#~ "to use a bridge, try the built-"
#~ "in obfs4 ones first."
#~ msgstr ""
#~ msgid ""
#~ "Pick a way to connect OnionShare "
#~ "to Tor by clicking the Tor onion"
#~ " icon in the bottom right of "
#~ "the OnionShare window to open the "
#~ "Tor Settings tab."
#~ msgstr ""
#~ msgid ""
#~ "Pick a way to connect OnionShare "
#~ "to Tor by clicking Network Settings "
#~ "from the welcome screen, or the "
#~ "Tor onion icon in the bottom right"
#~ " of the OnionShare window to open "
#~ "the Tor Settings tab."
#~ msgstr ""
#~ msgid "Getting Around Censorship"
#~ msgstr ""
#~ msgid ""
#~ "If your access to the internet is"
#~ " censored, you can configure OnionShare "
#~ "to connect to the Tor network "
#~ "using `Tor bridges <https://tb-"
#~ "manual.torproject.org/bridges/>`_. If OnionShare "
#~ "connects to Tor without one, you "
#~ "don't need to use a bridge."
#~ msgstr ""
#~ msgid ""
#~ "To use a bridge, open the Tor "
#~ "Settings tab. You must select \"Use "
#~ "the Tor version built into OnionShare\""
#~ " and check the \"Use a bridge\" "
#~ "checkbox."
#~ msgstr ""
#~ msgid ""
#~ "Open OnionShare and click the \"⚙\" "
#~ "icon in it. Under \"How should "
#~ "OnionShare connect to Tor?\" choose "
#~ "\"Connect using control port\", and set"
#~ " \"Control port\" to ``127.0.0.1`` and "
#~ "\"Port\" to ``9051``. Under \"Tor "
#~ "authentication settings\" choose \"Password\" "
#~ "and set the password to the "
#~ "control port password you picked above."
#~ " Click the \"Test Connection to Tor\""
#~ " button. If all goes well, you "
#~ "should see \"Connected to the Tor "
#~ "controller\"."
#~ msgstr ""
#~ msgid ""
#~ "Open OnionShare and click the \"⚙\" "
#~ "icon in it. Under \"How should "
#~ "OnionShare connect to Tor?\" choose "
#~ "\"Connect using socket file\", and set"
#~ " the socket file to be "
#~ "``/usr/local/var/run/tor/control.socket``. Under \"Tor "
#~ "authentication settings\" choose \"No "
#~ "authentication, or cookie authentication\". "
#~ "Click the \"Test Connection to Tor\" "
#~ "button."
#~ msgstr ""
#~ msgid ""
#~ "Reboot your computer. After it boots "
#~ "up again, open OnionShare and click "
#~ "the \"⚙\" icon in it. Under \"How"
#~ " should OnionShare connect to Tor?\" "
#~ "choose \"Connect using socket file\". "
#~ "Set the socket file to be "
#~ "``/var/run/tor/control``. Under \"Tor authentication"
#~ " settings\" choose \"No authentication, or"
#~ " cookie authentication\". Click the \"Test"
#~ " Connection to Tor\" button."
#~ msgstr ""