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

[bridgedb/develop] Merge branch 'master' into develop
by isis＠torproject.org 21 May '18

21 May '18

commit 2ec54aa253da7969166e7f4c4253a34b8dea833d Merge: 2a4ba64 e6ac1cc Author: Isis Lovecruft <isis(a)torproject.org> Date: Mon May 21 18:51:56 2018 +0000 Merge branch 'master' into develop

1 0

[bridgedb/master] Merge branch 'release/0.6.6'
by isis＠torproject.org 21 May '18

21 May '18

commit e6ac1ccaec294bf80ffc0694839ca562dd515d75 Merge: 9cfb469 2a4ba64 Author: Isis Lovecruft <isis(a)torproject.org> Date: Mon May 21 18:42:49 2018 +0000 Merge branch 'release/0.6.6' bridgedb/Bridges.py | 7 +++++++ 1 file changed, 7 insertions(+)

1 0

[bridgedb/master] Merge branch 'bug26150' into develop
by isis＠torproject.org 21 May '18

21 May '18

commit 2a4ba64a3d0c3f108c2fa25142edfcc3148d98e2 Merge: 85e4566 6db4d2b Author: Isis Lovecruft <isis(a)torproject.org> Date: Mon May 21 18:41:54 2018 +0000 Merge branch 'bug26150' into develop bridgedb/Bridges.py | 7 +++++++ 1 file changed, 7 insertions(+)

1 0

[bridgedb/develop] Merge branch 'bug26150' into develop
by isis＠torproject.org 21 May '18

21 May '18

commit 2a4ba64a3d0c3f108c2fa25142edfcc3148d98e2 Merge: 85e4566 6db4d2b Author: Isis Lovecruft <isis(a)torproject.org> Date: Mon May 21 18:41:54 2018 +0000 Merge branch 'bug26150' into develop bridgedb/Bridges.py | 7 +++++++ 1 file changed, 7 insertions(+)

1 0

[bridgedb/master] Merge branch 'master' into develop
by isis＠torproject.org 21 May '18

21 May '18

commit 85e45669568d82a0c238227fe2c5d2478ff15676 Merge: d9741cf 9cfb469 Author: Isis Lovecruft <isis(a)torproject.org> Date: Fri May 4 18:29:41 2018 +0000 Merge branch 'master' into develop

1 0

[bridgedb/develop] Hotfix for strange bridges missing address fields.
by isis＠torproject.org 21 May '18

21 May '18

commit 6db4d2beccab230bd40fb423da48ac2f336a5662 Author: Isis Lovecruft <isis(a)torproject.org> Date: Mon May 21 18:27:28 2018 +0000 Hotfix for strange bridges missing address fields. --- bridgedb/Bridges.py | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/bridgedb/Bridges.py b/bridgedb/Bridges.py index dfc6ac5..7257617 100644 --- a/bridgedb/Bridges.py +++ b/bridgedb/Bridges.py @@ -280,6 +280,13 @@ class BridgeRing(object): for fingerprint in fingerprints: bridge = self.bridges[fingerprint] jump = False + + # HOTFIX for https://bugs.torproject.org/26150 + if not bridge.address: + logging.error("Got strange bridge with no address field set: %s" + % fingerprint) + continue + for subnet in subnets: if bridge.address in subnet: jump = True

1 0

[bridgedb/master] Hotfix for strange bridges missing address fields.
by isis＠torproject.org 21 May '18

21 May '18

commit 6db4d2beccab230bd40fb423da48ac2f336a5662 Author: Isis Lovecruft <isis(a)torproject.org> Date: Mon May 21 18:27:28 2018 +0000 Hotfix for strange bridges missing address fields. --- bridgedb/Bridges.py | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/bridgedb/Bridges.py b/bridgedb/Bridges.py index dfc6ac5..7257617 100644 --- a/bridgedb/Bridges.py +++ b/bridgedb/Bridges.py @@ -280,6 +280,13 @@ class BridgeRing(object): for fingerprint in fingerprints: bridge = self.bridges[fingerprint] jump = False + + # HOTFIX for https://bugs.torproject.org/26150 + if not bridge.address: + logging.error("Got strange bridge with no address field set: %s" + % fingerprint) + continue + for subnet in subnets: if bridge.address in subnet: jump = True

1 0

[stem/master] Add Bine to list of alternate controller libraries
by atagar＠torproject.org 21 May '18

21 May '18

commit 23b8acc974d692066efdd92676651d15ebb63dd0 Author: Damian Johnson <atagar(a)torproject.org> Date: Mon May 21 09:33:23 2018 -0700 Add Bine to list of alternate controller libraries Go controller library from Chad Retz... https://lists.torproject.org/pipermail/tor-dev/2018-May/013183.html --- docs/faq.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/faq.rst b/docs/faq.rst index 7f65911c..958e5cf4 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -275,9 +275,10 @@ Library Language `Txtorcon <https://txtorcon.readthedocs.org/>`_ Python (Twisted) February 2012 - Present `TorCtl <https://gitweb.torproject.org/pytorctl.git>`_ Python July 2008 - November 2011 `TorUtils <https://github.com/dapphp/TorUtils>`_ PHP October 2015 - Present -`Puccinia <https://gitlab.com/amphetamine/puccinia/>`_ Rust October 2015 - Present +`Puccinia <https://gitlab.com/amphetamine/puccinia/>`_ Rust October 2015 - July 2017 `PHP TorCtl <https://github.com/dunglas/php-torcontrol/>`_ PHP February 2013 `JTorCtl <https://gitweb.torproject.org/jtorctl.git>`_ Java June 2005 - May 2009 +`Bine <https://github.com/cretz/bine>`_ Go May 2018 `Orc <https://github.com/sycamoreone/orc>`_ Go January 2015 `Bulb <https://github.com/Yawning/bulb>`_ Go March 2015 `Rust Controller <https://github.com/Dhole/rust-tor-controller>`_ Rust May 2016

1 0

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

21 May '18

commit 7cfd7f00bd1919a6715d728ceb339e47d11e6025 Author: Translation commit bot <translation(a)torproject.org> Date: Mon May 21 15:49:03 2018 +0000 Update translations for support-connecting_completed --- pt_BR.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pt_BR.json b/pt_BR.json index a1bf886e7..cb1197435 100644 --- a/pt_BR.json +++ b/pt_BR.json @@ -2,14 +2,14 @@ "connecting-1": { "id": "#conectando-1", "control": "conectando-1", - "title": "O Navegador Tor não se conectará, mas não parece ser um problema com a censura.", + "title": "O Tor Browser não está funcionando, mas não parece ser algo relacionado a censura.", "description": "<p class=\"mb-3\">Um dos problemas mais comuns que causa erros de conexão no Navegador Tor é um relógio do sistema incorreto. Por favor, certifique-se de que o relógio do sistema e o fuso horário estejam definidos com precisão. Se isso não resolver o problema, consulte a página Solução de Problemas no manual do Navegador Tor</a></mark>.</p>" }, "connecting-2": { "id": "#conectando-2", "control": "conectando-2", "title": "Estou tendo problemas para conectar com o Tor e não consigo descobrir o que está acontecendo de errado.", - "description": "<p class=\"mb-3\">Se estiver tendo problemas ao se conectar, por favor selecione a opção para \"copiar o log de Tor para a área de transferências\". Em seguida cole o log do Tor em um arquivo de texto ou outro documento. Você deverá ver um destes erros de logs comuns (procure as seguintes linhas no seu log do Tor):<h5>Erro de log comum #1: Falha na conexão de Proxy</h5><p class=\"mb-3\"><pre>2017-10-29 09:23:40.800 [OBSERVE] Opening Socks listener on 127.0.0.1:9150\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 5%: Conectando ao servidor do diretório\n2017-10-29 09:23:47.900 [OBSERVE] Bootstrapped 10%: Concluindo o 'handshake' com o servidor do diretório\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: não foi possível conectar-se à xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:08.900 [AVISO] Cliente: de Proxy: não foi possível conectar-se à xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\")\n2017-10-29 09:24:0 8.900 [AVISO] Cliente: de Proxy: não foi possível conectar-se à xx..xxx..xxx.xx:xxxxx (\"general SOCKS server failure\") Se você encontrar linhas como estas em seu log do Tor, isto significa que falhou em conectar-se à um SOCKS proxy. Se um SOCKS proxy é obrigatório para a sua configuração de rede, por favor certifique-se que você digitou seus detalhes de proxy corretamente. Se um SOCKS proxy não é obrigatório, ou você não está certo sobre isso, por favor tente conectar-se à rede Tor sem um SOCKS proxy. Common log error #2: Can’t reach guard relays 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.\n11/1/2017 21:11:44 PM.500 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop\n11/1/2017 21:11:45 PM.300 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.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.Common log error #3: Failed to complete TLS handshake 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)If you see lines like this in your Tor log, it means that Tor failed to complete a TLS hand shake with the directory authorities. Using bridges will likely fix this.Common log error #4: Clock skew 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\n19.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 requires an accurate clock to work: please check your time, timezone, and date settings.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. " + "description": "<p class=\"mb-3\">Se você estiver tendo dificuldades para se conectar, por favor selecione a opção \"copiar o log do Tor na área de trabalho\". Em seguida, copie o log to Tor em um arquivo de texto ou outro documento. Normalmente você verá um dos erros mais comuns (procure as seguintes linhas no seu log do Tor):</p><h5>Erros comuns #1: falha de conexão com o Proxy</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 failure\")</code></pre></p><p class=\"mb-3\">Se você vir mensagens como essas no seu log do Tor, é porque você nao esta se conectando a nenhum proxy SOCKS. Se um proxy SOCKS for necessário para configurar a sua rede, por favor, verifique se você inseriu os detalhes do proxy corretamente. 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. Discardi ng 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 rest art Tor. </p>" }, "connecting-3": { "id": "#conectando-3",

1 0

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

21 May '18

commit 458943fc5881dc3ff457bf93b5b5b3b275cca0dd Author: Translation commit bot <translation(a)torproject.org> Date: Mon May 21 15:48:58 2018 +0000 Update translations for support-connecting --- pt_BR.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pt_BR.json b/pt_BR.json index 222d00ffd..cb1197435 100644 --- a/pt_BR.json +++ b/pt_BR.json @@ -9,7 +9,7 @@ "id": "#conectando-2", "control": "conectando-2", "title": "Estou tendo problemas para conectar com o Tor e não consigo descobrir o que está acontecendo de errado.", - "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\">Se você estiver tendo dificuldades para se conectar, por favor selecione a opção \"copiar o log do Tor na área de trabalho\". Em seguida, copie o log to Tor em um arquivo de texto ou outro documento. Normalmente você verá um dos erros mais comuns (procure as seguintes linhas no seu log do Tor):</p><h5>Erros comuns #1: falha de conexão com o Proxy</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 failure\")</code></pre></p><p class=\"mb-3\">Se você vir mensagens como essas no seu log do Tor, é porque você nao esta se conectando a nenhum proxy SOCKS. Se um proxy SOCKS for necessário para configurar a sua rede, por favor, verifique se você inseriu os detalhes do proxy corretamente. 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. Discardi ng 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 rest art Tor. </p>" }, "connecting-3": { "id": "#conectando-3",

1 0