June 2018 - tor-commits - lists.torproject.org

[translation/bridgedb_completed] Update translations for bridgedb_completed
by translation＠torproject.org 21 Jun '18

21 Jun '18

commit 78be25b7cfb0fea4dce290ea28628c655e6259b9 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Jun 21 12:15:18 2018 +0000 Update translations for bridgedb_completed --- fi/LC_MESSAGES/bridgedb.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fi/LC_MESSAGES/bridgedb.po b/fi/LC_MESSAGES/bridgedb.po index 0c7e455bc..9da54daa4 100644 --- a/fi/LC_MESSAGES/bridgedb.po +++ b/fi/LC_MESSAGES/bridgedb.po @@ -19,8 +19,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2015-07-25 03:40+0000\n" -"PO-Revision-Date: 2018-04-12 18:54+0000\n" -"Last-Translator: IDRASSI Mounir <mounir.idrassi(a)idrix.fr>\n" +"PO-Revision-Date: 2018-06-21 12:02+0000\n" +"Last-Translator: Panu Ahvenharju <panu.ahvenharju(a)gmail.com>\n" "Language-Team: Finnish (http://www.transifex.com/otf/torproject/language/fi/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 21 Jun '18

21 Jun '18

commit 557c1e18c96c0e6f0b646429fe3eefa5a1ffeed8 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Jun 21 12:15:06 2018 +0000 Update translations for bridgedb --- fi/LC_MESSAGES/bridgedb.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fi/LC_MESSAGES/bridgedb.po b/fi/LC_MESSAGES/bridgedb.po index 0c7e455bc..9da54daa4 100644 --- a/fi/LC_MESSAGES/bridgedb.po +++ b/fi/LC_MESSAGES/bridgedb.po @@ -19,8 +19,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2015-07-25 03:40+0000\n" -"PO-Revision-Date: 2018-04-12 18:54+0000\n" -"Last-Translator: IDRASSI Mounir <mounir.idrassi(a)idrix.fr>\n" +"PO-Revision-Date: 2018-06-21 12:02+0000\n" +"Last-Translator: Panu Ahvenharju <panu.ahvenharju(a)gmail.com>\n" "Language-Team: Finnish (http://www.transifex.com/otf/torproject/language/fi/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n"

1 0

[tor-browser-build/master] Bug 26438: Remove seatbelt profiles for macOS
by boklm＠torproject.org 21 Jun '18

21 Jun '18

commit 767dd879b91584d5828998804ab1ee45499ca640 Author: Georg Koppen <gk(a)torproject.org> Date: Thu Jun 21 07:45:40 2018 +0000 Bug 26438: Remove seatbelt profiles for macOS Starting with content sandboxing being enabled our seatbelt profiles have been broken (see: #22000). We should remove them for now to avoid a broken experience in the alphas. --- .../tor-browser/Bundle-Data/mac-sandbox/.DS_Store | Bin 6148 -> 0 bytes .../tor-browser/Bundle-Data/mac-sandbox/README.txt | 29 ----- .../mac-sandbox/start-browser-with-sandbox | 24 ---- .../Bundle-Data/mac-sandbox/start-tor-with-sandbox | 42 ------- projects/tor-browser/Bundle-Data/mac-sandbox/tb.sb | 122 --------------------- .../tor-browser/Bundle-Data/mac-sandbox/tor.sb | 64 ----------- projects/tor-browser/build | 5 - 7 files changed, 286 deletions(-) diff --git a/projects/tor-browser/Bundle-Data/mac-sandbox/.DS_Store b/projects/tor-browser/Bundle-Data/mac-sandbox/.DS_Store deleted file mode 100644 index 6c49e24..0000000 Binary files a/projects/tor-browser/Bundle-Data/mac-sandbox/.DS_Store and /dev/null differ diff --git a/projects/tor-browser/Bundle-Data/mac-sandbox/README.txt b/projects/tor-browser/Bundle-Data/mac-sandbox/README.txt deleted file mode 100644 index 47d6e5c..0000000 --- a/projects/tor-browser/Bundle-Data/mac-sandbox/README.txt +++ /dev/null @@ -1,29 +0,0 @@ -Experimental Sandboxed Tor Browser for OS X - -Requirements: - Mac OS 10.9 or newer. - A willingness to run shell commands from Terminal. - -Follow these steps to use the sandbox profiles: - -1. Copy this folder ("Sandboxed Tor Browser") to a local drive, but do not - put it in /Applications. -2. Copy the TorBrowser app into your "Sandboxed Tor Browser" folder. -3. Open Terminal. -4. Run start-tor-with-sandbox and wait for Tor bootstrapping to finish. -5. Run start-browser-with-sandbox. - -Known Issues: - -You will need to manually kill start-tor-with-sandbox or the tor.real -process after you exit the browser. - -The browser has full access to the Tor control port. Ideally, access -would be limited to the things that are necessary for New Identity and -for the circuit display features. - -Printing does not work. - -The built-in updater will not work. - -Files can only be downloaded or saved to ~/Downloads. diff --git a/projects/tor-browser/Bundle-Data/mac-sandbox/start-browser-with-sandbox b/projects/tor-browser/Bundle-Data/mac-sandbox/start-browser-with-sandbox deleted file mode 100755 index 31d4218..0000000 --- a/projects/tor-browser/Bundle-Data/mac-sandbox/start-browser-with-sandbox +++ /dev/null @@ -1,24 +0,0 @@ -#!/bin/bash - -# TODO: assumes not in /Applications -# TODO: assumes app is in TorBrowser.app - -BASEDIR="`dirname \"$0\"`" -BASEDIR="`(cd \"$BASEDIR\" && pwd)`" -TORBROWSER_APP_DIR="$BASEDIR/TorBrowser.app" -TORBROWSER_DATA_DIR="$BASEDIR/TorBrowser-Data" -TOR_DATA_DIR="$TORBROWSER_DATA_DIR/Tor" -SOCKETDIR="/tmp/Tor" - -export TOR_SKIP_LAUNCH=1 -export TOR_CONTROL_IPC_PATH="$SOCKETDIR/control.socket" -export TOR_SOCKS_IPC_PATH="$SOCKETDIR/socks.socket" -export TOR_CONTROL_COOKIE_AUTH_FILE="$TOR_DATA_DIR/control_auth_cookie" -SB_PROFILE="`pwd`/tb.sb" -cd "$TORBROWSER_APP_DIR" -sandbox-exec -f "$SB_PROFILE" \ - -D "HOME_DIR=$HOME" \ - -D "CURRENT_DIR=$BASEDIR" \ - -D "TORBROWSER_APP_DIR=$TORBROWSER_APP_DIR" \ - -D "TORBROWSER_DATA_DIR=$TORBROWSER_DATA_DIR" \ - "./Contents/MacOS/firefox" diff --git a/projects/tor-browser/Bundle-Data/mac-sandbox/start-tor-with-sandbox b/projects/tor-browser/Bundle-Data/mac-sandbox/start-tor-with-sandbox deleted file mode 100755 index ec7f15e..0000000 --- a/projects/tor-browser/Bundle-Data/mac-sandbox/start-tor-with-sandbox +++ /dev/null @@ -1,42 +0,0 @@ -#!/bin/bash - -# TODO: assumes not in /Applications -# TODO: assumes /tmp/Tor is not used by anyone else. -# TODO: assumes app is in TorBrowser.app - -set -e - -BASEDIR="`dirname \"$0\"`" -BASEDIR="`(cd \"$BASEDIR\" && pwd)`" -TOR_DATA_DIR="$BASEDIR/TorBrowser-Data/Tor" -TOR_STATIC_DATA_DIR="$BASEDIR/TorBrowser.app/Contents/Resources/TorBrowser/Tor" -TOR_BIN_DIR="$BASEDIR/TorBrowser.app/Contents/MacOS/Tor" -TORRC="$TOR_DATA_DIR/torrc" -SOCKETDIR="/tmp/Tor" - -# Compiled Python modules require a compatible Python, which means 32-bit 2.6. -export VERSIONER_PYTHON_VERSION=2.6 -export DYLD_LIBRARY_PATH=.:$DYLD_LIBRARY_PATH - -mkdir -p "$TOR_DATA_DIR" -if [ ! -e "$TORRC" ]; then - touch "$TORRC" -fi - -if [ ! -e "$SOCKETDIR" ]; then - mkdir -p "$SOCKETDIR" - chmod 700 "$SOCKETDIR" -fi - -TOR="$TOR_BIN_DIR/tor.real" -sandbox-exec -f tor.sb -D "TOR_DATA_DIR=$TOR_DATA_DIR" \ - -D "TOR_STATIC_DATA_DIR=$TOR_STATIC_DATA_DIR" \ - -D "TOR_BIN_DIR=$TOR_BIN_DIR" "$TOR" \ - --defaults-torrc "$TOR_STATIC_DATA_DIR/torrc-defaults" \ - -f "$TORRC" \ - CookieAuthentication 1 \ - DataDirectory "$TOR_DATA_DIR" \ - GeoIPFile "$TOR_STATIC_DATA_DIR/geoip" \ - GeoIPv6File "$TOR_STATIC_DATA_DIR/geoip6" \ - ControlPort "unix:$SOCKETDIR/control.socket" \ - SocksPort "unix:$SOCKETDIR/socks.socket" diff --git a/projects/tor-browser/Bundle-Data/mac-sandbox/tb.sb b/projects/tor-browser/Bundle-Data/mac-sandbox/tb.sb deleted file mode 100644 index 385e914..0000000 --- a/projects/tor-browser/Bundle-Data/mac-sandbox/tb.sb +++ /dev/null @@ -1,122 +0,0 @@ -(version 1) - -;; Parameters: -;; HOME_DIR the user's home directory -;; CURRENT_DIR the current working directory -;; TORBROWSER_APP_DIR the TorBrowser.app directory -;; TORBROWSER_DATA_DIR the TorBrowser-Data directory - -;; TODO: can see all dirs but can download/save only in Downloads (no error reported though!) -;; TODO: printing does not work (Save to PDF does). - -(deny default) - -(define (home-path aSubPath) - (path (string-append (param "HOME_DIR") aSubPath))) - -(define (home-subpath aSubPath) - (subpath (string-append (param "HOME_DIR") aSubPath))) - -(define (torbrowser-data-dir-path aSubPath) - (path (string-append (param "TORBROWSER_DATA_DIR") aSubPath))) - -(define (torbrowser-data-dir-subpath aSubPath) - (subpath (string-append (param "TORBROWSER_DATA_DIR") aSubPath))) - -(define (torbrowser-app-dir-path aSubPath) - (subpath (string-append (param "TORBROWSER_APP_DIR") aSubPath))) - -(allow file-read* - (path "/Library/Preferences/com.apple.HIToolbox.plist") - (path "/Library/Preferences/com.apple.ViewBridge.plist") - (path "/Library/Preferences/.GlobalPreferences.plist") - (path "/dev/random") - (path "/dev/urandom") - (path "/dev/dtracehelper") - (path "/private/etc/localtime") - (path "/private/etc/passwd") - (path "/private/tmp") - (path "/private/var/tmp") - (path (param "HOME_DIR")) - (subpath "/Library/Audio") - (subpath "/Library/Fonts") - (subpath "/System") - (subpath "/private/var/folders") - (subpath "/usr/lib") - (subpath "/usr/share") - (home-subpath "/Downloads") - (home-subpath "/Library/Input Methods") - (home-subpath "/Library/Keyboard Layouts") - (home-subpath "/Library/Preferences") - (torbrowser-app-dir-path "") - (torbrowser-data-dir-path "") - (torbrowser-data-dir-subpath "/Browser") - (torbrowser-data-dir-path "/Tor/control_auth_cookie") -) - -(allow file-read-metadata - (home-path "/Desktop") - (home-path "/Library") - (home-path "/Library/Saved Application State") - (path (param "CURRENT_DIR")) - (path "/") - (path "/Applications") - (path "/Users") - (path "/etc") - (path "/home") - (path "/net") - (path "/private/var/db/.AppleSetupDone") - (path "/tmp") - (path "/var") - (torbrowser-data-dir-path "/Tor/control.socket") - (torbrowser-data-dir-path "/Tor/socks.socket") - (path-regex "/private/tmp/Tor[-0-9]*/control.socket") - (path-regex "/private/tmp/Tor[-0-9]*/socks.socket") -) - -(allow file-write-data file-ioctl - (path "/dev/dtracehelper") -) - -(allow file-write* - (home-subpath "/Downloads") - (home-path "/Library/Preferences/.GlobalPreferences.plist") - (torbrowser-data-dir-subpath "/Browser") - (subpath "/private/var/folders") - (path-regex (string-append "^" (param "HOME_DIR") "/Library/Preferences/org.mozilla.tor")) - (path "/Library/Preferences/.GlobalPreferences.plist") -) - -(allow iokit-open) - -(allow ipc-posix-shm - (ipc-posix-name "apple.shm.notification_center") - (ipc-posix-name-regex "^/tmp/com.apple.csseed") - (ipc-posix-name-regex "^CFPBS:") - (ipc-posix-name-regex "^apple\.cfprefs\.") - (ipc-posix-name-regex "^apple\.shm\.cfprefs\.") - (ipc-posix-name-regex "^AudioIO") -) - -(allow mach-lookup) - -(allow mach-register - (local-name "com.apple.CFPasteboardClient") - (local-name "com.apple.axserver") - (local-name "com.apple.coredrag") - (local-name "com.apple.tsm.portname") -) - -(allow network-outbound - (path "/private/var/run/cupsd") - (torbrowser-data-dir-path "/Tor/control.socket") - (torbrowser-data-dir-path "/Tor/socks.socket") - (path-regex "/private/tmp/Tor[-0-9]*/control.socket") - (path-regex "/private/tmp/Tor[-0-9]*/socks.socket") -) - -(allow process-exec* - (torbrowser-app-dir-path "/Contents/MacOS/firefox") -) - -(allow sysctl-read) diff --git a/projects/tor-browser/Bundle-Data/mac-sandbox/tor.sb b/projects/tor-browser/Bundle-Data/mac-sandbox/tor.sb deleted file mode 100644 index 40abc9c..0000000 --- a/projects/tor-browser/Bundle-Data/mac-sandbox/tor.sb +++ /dev/null @@ -1,64 +0,0 @@ -(version 1) - -;; Parameters: -;; TOR_DATA_DIR directory that contains writeable config, e.g, torrc -;; TOR_STATIC_DATA_DIR directory for read-only config, e.g., torrc-defaults -;; TOR_BIN_DIR directory that contains tor binaries, e.g., tor.real - -(deny default) - -(allow file-read* file-write-data file-ioctl - (path "/dev/dtracehelper") -) - -(allow file-read* - (subpath (param "TOR_BIN_DIR")) - (subpath "/usr/local") - (subpath (param "TOR_DATA_DIR")) - (subpath (param "TOR_STATIC_DATA_DIR")) - (subpath (param "TOR_BIN_DIR")) - (path-regex "/private/tmp/Tor[-0-9]*") -) - -(allow file-read-data - (path "/dev/random") - (path "/dev/srandom") - (path "/dev/urandom") - (subpath "/usr/share") -) - -(allow file-read-metadata - (path "/etc") - (path "/private/etc/localtime") - (path "/tmp") - (subpath "/usr/lib") -) - -(allow file-write* - (subpath (param "TOR_DATA_DIR")) -) - -(allow ipc-posix-shm-read-data - (ipc-posix-name "apple.shm.notification_center") -) - -(allow mach-lookup - (global-name "com.apple.system.notification_center") -) - -(allow network-inbound file-write* - (path (string-append (param "TOR_DATA_DIR") "/control.socket")) - (path (string-append (param "TOR_DATA_DIR") "/socks.socket")) - (path-regex "/private/tmp/Tor[-0-9]*/control.socket") - (path-regex "/private/tmp/Tor[-0-9]*/socks.socket") -) - -(allow network-outbound - (remote tcp "*:*") -) - -(allow process-exec - (path (string-append (param "TOR_BIN_DIR") "/tor.real")) -) - -(allow sysctl-read) diff --git a/projects/tor-browser/build b/projects/tor-browser/build index 65c752b..1c98c35 100644 --- a/projects/tor-browser/build +++ b/projects/tor-browser/build @@ -105,11 +105,6 @@ tar -C "$TBDIR[% IF ! c("var/osx") %]/TorBrowser[% END %]" -xf [% c('input_files mv "$TBDIR/$TORBINPATH/tor" "$TBDIR/$TORBINPATH/tor.real" cp Bundle-Data/mac-tor.sh "$TBDIR/$TORCONFIGPATH/tor" - [% IF ! c("var/release") -%] - SANDBOX_FOLDER="$TB_STAGE_DIR/Sandboxed Tor Browser" - mv Bundle-Data/mac-sandbox "$SANDBOX_FOLDER" - [% END -%] - tar -C Bundle-Data/mac-applications.dmg -c . | tar -C $TB_STAGE_DIR -x [% END %]

1 0

[tor-browser-build/master] Bug 26438: Use non-sandbox background and .DS_Store again
by boklm＠torproject.org 21 Jun '18

21 Jun '18

commit 8b91968072326cf32da011b2c8bd3bbef14e4ef4 Author: Georg Koppen <gk(a)torproject.org> Date: Thu Jun 21 08:44:02 2018 +0000 Bug 26438: Use non-sandbox background and .DS_Store again --- .../Bundle-Data/mac-applications.dmg/.DS_Store | Bin 12292 -> 12292 bytes .../mac-applications.dmg/.background/background.png | Bin 49906 -> 50020 bytes 2 files changed, 0 insertions(+), 0 deletions(-) diff --git a/projects/tor-browser/Bundle-Data/mac-applications.dmg/.DS_Store b/projects/tor-browser/Bundle-Data/mac-applications.dmg/.DS_Store index 6eeec47..aeb3104 100644 Binary files a/projects/tor-browser/Bundle-Data/mac-applications.dmg/.DS_Store and b/projects/tor-browser/Bundle-Data/mac-applications.dmg/.DS_Store differ diff --git a/projects/tor-browser/Bundle-Data/mac-applications.dmg/.background/background.png b/projects/tor-browser/Bundle-Data/mac-applications.dmg/.background/background.png index a4358cf..94e4584 100644 Binary files a/projects/tor-browser/Bundle-Data/mac-applications.dmg/.background/background.png and b/projects/tor-browser/Bundle-Data/mac-applications.dmg/.background/background.png differ

1 0

[translation/support-censorship] Update translations for support-censorship
by translation＠torproject.org 21 Jun '18

21 Jun '18

commit 133b2543248996ce7be8951c02c85f63334f6fae Author: Translation commit bot <translation(a)torproject.org> Date: Thu Jun 21 07:48:57 2018 +0000 Update translations for support-censorship --- fi.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi.json b/fi.json index ab2506569..aea3ea933 100644 --- a/fi.json +++ b/fi.json @@ -27,7 +27,7 @@ "id": "#censorship-5", "control": "censorship-5", "title": "Minulla on ongelmia yhdistÃ€essÃ€ Tor:iin enkÃ€ keksi mikÃ€ voisi olla vialla.", - "description": "<p class=\"mb-3\"><p class=\"mb-3\">Jos sinulla on yhdistÃ€misongelmia niin ole hyvÃ€ ja valitse \"kopio Tor-logi leikepÃ¶ydÃ€lle.\" TÃ€mÃ€n jÃ€lkeen liitÃ€ Tor-logi tyhjÃ€Ã€n tekstitiedostoon tai muuhun dokumenttiin. Sinun pitÃ€isi nÃ€hdÃ€ joku nÃ€istÃ€ yleisistÃ€ log-virheistÃ€ (etsi seuraavia rivejÃ€ Tor-logista): </p> Yleinen log-virhe #1 Proxy-yhteysvirhe <h5><p class=\"mb-3\"><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") </code><pre></pre><p class=\"mb-3\"> Jos nÃ€et tÃ€llÃ€isiÃ€ rivejÃ€ Tor-logissasi, tÃ€ mÃ€ tarkoittaa, ettÃ€ et saa yhdistettyÃ€ SOCKS-proxyyn. Jos verkkoasetuksesi tarvitsevat SOCKS-proxya varmista, ettÃ€ olet laittanut proxy-tiedot oikein. Jos SOCKS-proxyÃ€ ei vaadita tai et ole varma tarvitaanko, yritÃ€ yhdistÃ€Ã€ TOR-verkkoon ilman SOCKS-proxyÃ€. <p><h5>Yleinen log-virhe #2 Ei saa yhteyttÃ€ guard relayhin</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p> Jos Tor-logissasi on seuraavanlaisia rivejÃ€, tÃ€mÃ€ tarkoittaa sitÃ€, ettÃ€ Tor ei saanut yhdistettyÃ€ ensimmÃ€iseen nodeen Tor-ympyrÃ€ssÃ€. TÃ€mÃ€ voi tarkoittaa sitÃ€, ettÃ€ olet verkossa jota sensuroidaan. Ole hyvÃ€ ja kokeile yhdistÃ€Ã€ siltojen avulla. TÃ€mÃ€n pitÃ€isi korjata ongelma. </p> Yleinen log-virhe #1 Virhe viimeisteltÃ€essÃ€ TLS-kÃ€ttelyÃ€. <h5><p class=\"mb-3\"><pre><code>13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object) </code></pre><p class=\"mb-3\"> TÃ€llÃ€iset rivit Tor-logissa viittaavat ette Tor saanut viimeisteltyÃ€ TLS kÃ€ttelyÃ€ hakemistoviranomaisten kanssa. Siltojen kÃ€yttÃ¶ todennÃ€kÃ¶isesti korjaa tÃ€mÃ €n. </p> Yleinen log-virhe #4 Kellon vÃ€Ã€ristymÃ€ <h5><p class=\"mb-3\"><pre><code>" + "description": "<p class=\"mb-3\"><p class=\"mb-3\">Jos sinulla on yhdistÃ€misongelmia niin ole hyvÃ€ ja valitse \"kopio Tor-logi leikepÃ¶ydÃ€lle.\" TÃ€mÃ€n jÃ€lkeen liitÃ€ Tor-logi tyhjÃ€Ã€n tekstitiedostoon tai muuhun dokumenttiin. Sinun pitÃ€isi nÃ€hdÃ€ joku nÃ€istÃ€ yleisistÃ€ log-virheistÃ€ (etsi seuraavia rivejÃ€ Tor-logista): </p> Yleinen log-virhe #1 Proxy-yhteysvirhe <h5><p class=\"mb-3\"><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") </code><pre></pre><p class=\"mb-3\"> Jos nÃ€et tÃ€llÃ€isiÃ€ rivejÃ€ Tor-logissasi, tÃ€ mÃ€ tarkoittaa, ettÃ€ et saa yhdistettyÃ€ SOCKS-proxyyn. Jos verkkoasetuksesi tarvitsevat SOCKS-proxya varmista, ettÃ€ olet laittanut proxy-tiedot oikein. Jos SOCKS-proxyÃ€ ei vaadita tai et ole varma tarvitaanko, yritÃ€ yhdistÃ€Ã€ TOR-verkkoon ilman SOCKS-proxyÃ€. <p><h5>Yleinen log-virhe #2 Ei saa yhteyttÃ€ guard relayhin</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p> Jos Tor-logissasi on seuraavanlaisia rivejÃ€, tÃ€mÃ€ tarkoittaa sitÃ€, ettÃ€ Tor ei saanut yhdistettyÃ€ ensimmÃ€iseen nodeen Tor-ympyrÃ€ssÃ€. TÃ€mÃ€ voi tarkoittaa sitÃ€, ettÃ€ olet verkossa jota sensuroidaan. Ole hyvÃ€ ja kokeile yhdistÃ€Ã€ siltojen avulla. TÃ€mÃ€n pitÃ€isi korjata ongelma. </p> Yleinen log-virhe #1 Virhe viimeisteltÃ€essÃ€ TLS-kÃ€ttelyÃ€. <h5><p class=\"mb-3\"><pre><code>13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object) </code></pre><p class=\"mb-3\"> TÃ€llÃ€iset rivit Tor-logissa viittaavat ette Tor saanut viimeisteltyÃ€ TLS kÃ€ttelyÃ€ hakemistoviranomaisten kanssa. Siltojen kÃ€yttÃ¶ todennÃ€kÃ¶isesti korjaa tÃ€mÃ €n. </p> Yleinen log-virhe #4 Kellon vÃ€Ã€ristymÃ€ <h5><p class=\"mb-3\">19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150Â \n19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n9.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \nTor vaatii tarkan ajan kelloon toimiakseen. Ole hyvÃ€ ja tarkista aika ja aikavyÃ¶hyke, sekÃ€ pÃ€ivÃ€ys asetukset. <code><pre></pre><p class=\"mb-3\">. Jos nÃ€et tÃ€llÃ€isiÃ€ rivejÃ€ Tor-logissa se tarkoittaa, ettÃ€ kellosi on vÃ€Ã€rÃ€ssÃ€ ajassa. Ole hyvÃ€ ja korjaa kellonaika tarkasti sisÃ€ltÃ€en oikean aikavyÃ¶hykkeen. TÃ€mÃ€n jÃ€lkeen kÃ€ynnistÃ€ Tor uudelleen.</p>" }, "censorship-6": { "id": "#censorship-6",

1 0

[translation/support-connecting] Update translations for support-connecting
by translation＠torproject.org 21 Jun '18

21 Jun '18

commit 15915355178faab25d49a2c80f945ff0f07cb771 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Jun 21 07:19:06 2018 +0000 Update translations for support-connecting --- fi.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi.json b/fi.json index 4093d10aa..a498133a4 100644 --- a/fi.json +++ b/fi.json @@ -9,7 +9,7 @@ "id": "#connecting-2", "control": "connecting-2", "title": "Minulla on ongelmia yhdistÃ€essÃ€ Tor:iin enkÃ€ keksi mikÃ€ voisi olla vialla.", - "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to \"copy Tor log to clipboard.\" Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server fa ilure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that Tor failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + "description": "<p class=\"mb-3\">Jos sinulla on yhdistÃ€misongelmia niin ole hyvÃ€ ja valitse \"kopio Tor-logi leikepÃ¶ydÃ€lle.\" TÃ€mÃ€n jÃ€lkeen liitÃ€ Tor-logi tyhjÃ€Ã€n tekstitiedostoon tai muuhun dokumenttiin. Sinun pitÃ€isi nÃ€hdÃ€ joku nÃ€istÃ€ yleisistÃ€ log-virheistÃ€ (etsi seuraavia rivejÃ€ Tor-logista): </p> Yleinen log-virhe #1 Proxy-yhteysvirhe <h5><p class=\"mb-3\"><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") </code><pre></p><p class=\"mb-3\"> Jos nÃ€et tÃ€llÃ€isiÃ€ rivejÃ€ Tor-logissasi, tÃ€mÃ€ tarkoittaa, ettÃ € et saa yhdistettyÃ€ SOCKS" }, "connecting-3": { "id": "#connecting-3",

1 0

[translation/support-censorship] Update translations for support-censorship
by translation＠torproject.org 21 Jun '18

21 Jun '18

commit 534c77bd61178a47bee7701f673d5091a3337aa8 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Jun 21 07:18:58 2018 +0000 Update translations for support-censorship --- fi.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi.json b/fi.json index 886a1a23d..ab2506569 100644 --- a/fi.json +++ b/fi.json @@ -27,7 +27,7 @@ "id": "#censorship-5", "control": "censorship-5", "title": "Minulla on ongelmia yhdistÃ€essÃ€ Tor:iin enkÃ€ keksi mikÃ€ voisi olla vialla.", - "description": "<p class=\"mb-3\">If youâre having trouble connecting, please select the option to \"copy Tor log to clipboard.\" Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server fa ilure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure youâve entered your proxy details correctly. If a SOCKS proxy is not required, or youâre not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Canât reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that youâre on a network thatâs censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that Tor failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" + "description": "<p class=\"mb-3\"><p class=\"mb-3\">Jos sinulla on yhdistÃ€misongelmia niin ole hyvÃ€ ja valitse \"kopio Tor-logi leikepÃ¶ydÃ€lle.\" TÃ€mÃ€n jÃ€lkeen liitÃ€ Tor-logi tyhjÃ€Ã€n tekstitiedostoon tai muuhun dokumenttiin. Sinun pitÃ€isi nÃ€hdÃ€ joku nÃ€istÃ€ yleisistÃ€ log-virheistÃ€ (etsi seuraavia rivejÃ€ Tor-logista): </p> Yleinen log-virhe #1 Proxy-yhteysvirhe <h5><p class=\"mb-3\"><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") </code><pre></pre><p class=\"mb-3\"> Jos nÃ€et tÃ€llÃ€isiÃ€ rivejÃ€ Tor-logissasi, tÃ€ mÃ€ tarkoittaa, ettÃ€ et saa yhdistettyÃ€ SOCKS-proxyyn. Jos verkkoasetuksesi tarvitsevat SOCKS-proxya varmista, ettÃ€ olet laittanut proxy-tiedot oikein. Jos SOCKS-proxyÃ€ ei vaadita tai et ole varma tarvitaanko, yritÃ€ yhdistÃ€Ã€ TOR-verkkoon ilman SOCKS-proxyÃ€. <p><h5>Yleinen log-virhe #2 Ei saa yhteyttÃ€ guard relayhin</h5><p class=\"mb-3\"><pre><code>11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150\n11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p> Jos Tor-logissasi on seuraavanlaisia rivejÃ€, tÃ€mÃ€ tarkoittaa sitÃ€, ettÃ€ Tor ei saanut yhdistettyÃ€ ensimmÃ€iseen nodeen Tor-ympyrÃ€ssÃ€. TÃ€mÃ€ voi tarkoittaa sitÃ€, ettÃ€ olet verkossa jota sensuroidaan. Ole hyvÃ€ ja kokeile yhdistÃ€Ã€ siltojen avulla. TÃ€mÃ€n pitÃ€isi korjata ongelma. </p> Yleinen log-virhe #1 Virhe viimeisteltÃ€essÃ€ TLS-kÃ€ttelyÃ€. <h5><p class=\"mb-3\"><pre><code>13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server\n13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object) </code></pre><p class=\"mb-3\"> TÃ€llÃ€iset rivit Tor-logissa viittaavat ette Tor saanut viimeisteltyÃ€ TLS kÃ€ttelyÃ€ hakemistoviranomaisten kanssa. Siltojen kÃ€yttÃ¶ todennÃ€kÃ¶isesti korjaa tÃ€mÃ €n. </p> Yleinen log-virhe #4 Kellon vÃ€Ã€ristymÃ€ <h5><p class=\"mb-3\"><pre><code>" }, "censorship-6": { "id": "#censorship-6",

1 0

[translation/support-tbb] Update translations for support-tbb
by translation＠torproject.org 21 Jun '18

21 Jun '18

commit 62ad374aefe73e99beb7b1083f30b068440af978 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Jun 21 06:50:01 2018 +0000 Update translations for support-tbb --- fi.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi.json b/fi.json index 41e13c017..1122cc6a0 100644 --- a/fi.json +++ b/fi.json @@ -117,7 +117,7 @@ "id": "#tbb-19", "control": "tbb-19", "title": "En voi yhdistää Tor Browseriin, onko verkkoni sensuroitu?", - "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>" + "description": "<p class=\"mb-3\">Voi olla, että olet sensuroidussa verkossa, joten sinun tulisi koittaa käyttää siltoja. Jotkut sillat ovat sisäänrakennettuja Tor Selaimeen, ja voit käyttää noita siltoja valitsemalla \"configure\" (sitten seuraamalla kehotuksia) Tor Launcherin Ikkuna joka avautuu kun käynnistät Tor Browser :in ensimmäistä kertaa. Jos tarvitset muita siltoja, saat niitä meidän <mark><a href=\"https://bridges.torproject.org/\"> Bridges verkkosivu:lta</a></mark>. Lisätietoa silloista ja niiden käytöstä, katso <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Selamen manuaalista</a></mark>.</p>" }, "tbb-20": { "id": "#tbb-20",

1 0

[translation/support-connecting] Update translations for support-connecting
by translation＠torproject.org 21 Jun '18

21 Jun '18

commit c622b927750162b22b4cad85dec04e9bdaa80903 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Jun 21 06:49:16 2018 +0000 Update translations for support-connecting --- fi.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fi.json b/fi.json index 4d3e7f911..4093d10aa 100644 --- a/fi.json +++ b/fi.json @@ -8,7 +8,7 @@ "connecting-2": { "id": "#connecting-2", "control": "connecting-2", - "title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.", + "title": "Minulla on ongelmia yhdistäessä Tor:iin enkä keksi mikä voisi olla vialla.", "description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to \"copy Tor log to clipboard.\" Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server fa ilure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly. If a SOCKS proxy is not required, or you’re not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that Tor failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" }, "connecting-3": {

1 0

[translation/support-censorship] Update translations for support-censorship
by translation＠torproject.org 21 Jun '18

21 Jun '18

commit 641ef045c32ff46428bee9e0bf04a9724e351bcf Author: Translation commit bot <translation(a)torproject.org> Date: Thu Jun 21 06:49:07 2018 +0000 Update translations for support-censorship --- fi.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/fi.json b/fi.json index 8fc67c737..886a1a23d 100644 --- a/fi.json +++ b/fi.json @@ -21,19 +21,19 @@ "id": "#censorship-4", "control": "censorship-4", "title": "En voi yhdistää Tor Selaimeen, onko verkkoni sensuroitu?", - "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>" + "description": "<p class=\"mb-3\">Voi olla, että olet sensuroidussa verkossa, joten sinun tulisi koittaa käyttää siltoja. Jotkut sillat ovat sisäänrakennettuja Tor Selaimeen, ja voit käyttää noita siltoja valitsemalla \"configure\" (sitten seuraamalla kehotuksia) Tor Launcherin Ikkuna joka avautuu kun käynnistät Tor Browser :in ensimmäistä kertaa. Jos tarvitset muita siltoja, saat niitä meidän <mark><a href=\"https://bridges.torproject.org/\"> Bridges verkkosivu:lta</a></mark>. Lisätietoa silloista ja niiden käytöstä, katso <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Selamen manuaalista</a></mark>.</p>" }, "censorship-5": { "id": "#censorship-5", "control": "censorship-5", - "title": "I am having trouble connecting to Tor, and I can’t figure out what’s wrong.", + "title": "Minulla on ongelmia yhdistäessä Tor:iin enkä keksi mikä voisi olla vialla.", "description": "<p class=\"mb-3\">If you’re having trouble connecting, please select the option to \"copy Tor log to clipboard.\" Then paste the Tor log into a text file or other document. You should see one of these common log errors (look for the following lines in your Tor log):</p><h5>Common log error #1: Proxy connection failure</h5><p class=\"mb-3\"><pre><code> 2017-10-29 09:23:40.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 2017-10-29 09:23:47.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect to xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") \n 2017-10-29 09:24:08.900 [WARN] Proxy Client: unable to connect toxx..xxx..xxx.xx:xxxxx (\"general SOCKS server fa ilure\")</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means you are failing to connect to a SOCKS proxy. If a SOCKS proxy is required for your network setup, then please make sure you’ve entered your proxy details correctly. If a SOCKS proxy is not required, or you’re not sure, please try connecting to the Tor network without a SOCKS proxy.<p><h5>Common log error #2: Can’t reach guard relays</h5><p class=\"mb-3\"><pre><code> 11/1/2017 21:11:43 PM.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 11/1/2017 21:11:44 PM.300 [NOTICE] Bootstrapped 80%: Connecting to the Tor network \n 11/1/2017 21:11:44 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit. \n 11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop \n 11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.</code></pre></p><p class=\"mb-3\">If you see lines like these in your Tor log, it means your Tor failed to connect to the first node in the Tor circuit. This could mean that you’re on a network that’s censored. Please try connecting with bridges, and that should fix the problem.</p><h5>Common log error #3: Failed to complete TLS handshake</h5><p class=\"mb-3\"><pre><code> 13-11-17 19:52:24.300 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 13-11-17 19:53:49.300 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 10; recommendation warn; host [host] at xxx.xxx.xxx.xx:xxx) \n 13-11-17 19:53:49.300 [WARN] 10 connections have failed: \n 13-11-17 19:53:49.300 [WARN] 9 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE \n 13-11-17 19:53:49.300 [WARN] 1 connections died in state connect()ing with SSL state (No SSL object)</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means that Tor failed to complete a TLS handshake with the directory authorities. Using bridges will likely fix this.</p><h5>Common log error #4: Clock skew</h5><p class=\"mb-3\"><pre><code> 19.11.2017 00:04:47.400 [NOTICE] Opening Socks listener on 127.0.0.1:9150 \n 19.11.2017 00:04:48.000 [NOTICE] Bootstrapped 5%: Connecting to directory server \n 19.11.2017 00:04:48.200 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server \n 19.11.2017 00:04:48.800 [WARN] Received NETINFO cell with skewed time (OR:xxx.xx.x.xx:xxxx): It seems that our clock is behind by 1 days, 0 hours, 1 minutes, or that theirs is ahead. \n Tor requires an accurate clock to work: please check your time, timezone, and date settings.</code></pre></p><p class=\"mb-3\">If you see lines like this in your Tor log, it means your system clock is incorrect. Please make sure your clock is set accurately, including the correct timezone. Then restart Tor. </p>" }, "censorship-6": { "id": "#censorship-6", "control": "censorship-6", "title": "En voi yhdistää Tor Browseriin, onko verkkoni sensuroitu?", - "description": "<p class=\"mb-3\">You might be on a censored network, and so you should try using bridges. Some bridges are built in to Tor Browser, and you can use those bridges by choosing \"configure\" (then following the prompts) in the Tor Launcher window that pops up when you open Tor Browser for the first time. If you need other bridges, you can get them at our <mark><a href=\"https://bridges.torproject.org/\">Bridges website</a></mark>. For more information about bridges, see the <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\">Tor Browser manual</a></mark>.</p>" + "description": "<p class=\"mb-3\">Voi olla, että olet sensuroidussa verkossa, joten sinun tulisi koittaa käyttää siltoja. Jotkut sillat ovat sisäänrakennettuja Tor Selaimeen, ja voit käyttää noita siltoja valitsemalla \"configure\" (sitten seuraamalla kehotuksia) Tor Launcherin Ikkuna joka avautuu kun käynnistät Tor Browser :in ensimmäistä kertaa. Jos tarvitset muita siltoja, saat niitä meidän <mark><a href=\"https://bridges.torproject.org/\"> Bridges verkkosivu:lta</a></mark>. Lisätietoa silloista ja niiden käytöstä, katso <mark><a href=\"https://tb-manual.torproject.org/en-US/bridges.html\"> Tor Selamen manuaalista</a></mark>.</p>" }

1 0