tor-commits April 2018

tor-commits@lists.torproject.org

17 participants
1638 discussions

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

21 Apr '18

commit 9eb87c0b9688059f0b334d85d2a6350c3d1a2c30 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Apr 21 04:49:54 2018 +0000 Update translations for support-connecting --- zh_CN.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh_CN.json b/zh_CN.json index 19d37ef0e..f70a3941e 100644 --- a/zh_CN.json +++ b/zh_CN.json @@ -9,7 +9,7 @@ "id": "#è¿æ¥-2", "control": "è¿æ¥-2", "title": "æ æ³è¿æ¥å° TorïŒæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", - "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\\\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥</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\\\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</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\\\">åŠææšçè§è¿äºæç€ºåº ç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§æ¥å¿éè¯¯#3: TLSæ¡æå€±èŽ¥</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\\\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor ä žäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5> åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯</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. \\nToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœãè¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ã</code></pre></p><p class=\\\"mb-3\\\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" }, "connecting-3": { "id": "#è¿æ¥-3",

1 0

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

21 Apr '18

commit ae1f88db80adf35d568254062ffa329535f925d6 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Apr 21 04:49:50 2018 +0000 Update translations for support-censorship_completed --- zh_CN.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh_CN.json b/zh_CN.json index 69f34533c..77e144e42 100644 --- a/zh_CN.json +++ b/zh_CN.json @@ -9,7 +9,7 @@ "id": "#å®¡æ¥-2", "control": "å®¡æ¥-2", "title": "ææç±ççœç«å±èœæ¥èª Tor çè®¿é®ã", - "description": "<p class=\"mb-3\">äžèœè®¿é®äœ æ³èŠççœç«çæ¯éæŸå¢ïŒæäºçœç«å±èœäº Tor å äžºä»ä»¬æ æ³åèŸšåºæ®é Tor çšæ·åæºåšäººçåºå«ãæ ¹æ®è¿å»çç»éªïŒæ³èŠè®©çœç«è§£å°æ¥èª Tor çè®¿é®æææçæ¹æ³æ¯ç±çšæ·çŽæ¥èç³»çœç«ç®¡çåãä¹è®žè¿æ ·çæ¶æ¯å°±å¯ä»¥æåïŒ<br />âåšïŒåšçš Tor Browser çæ¶ååç°äœ ççœç« xyz.com äžåè®žæ¥èª Tor çè®¿é®ïŒåžæäœ å¯ä»¥éæ°èèè¿äžªå³å®ãåšçåå°åŸå€äººéœåšäœ¿çš Tor æ¥ä¿æ€éç§åå¯¹æå®¡æ¥ïŒå±èœ Tor çåæ¶äœ ä¹å±èœäºåŒºæåœå®¶äžæ³èªç±è®¿é®äºèçœççšæ·ãéèŠéèèªå·±çè®°èåæ£äžŸèãæ³èº²é¿çœç»è·èžªçç ç©¶èåæ®éçšæ·ãè¯·ç«åšæ¯æåšçº¿éç§åçœç»èªç±çç«åºäžïŒåè®ž Tor çšæ·è®¿é® xyz.comïŒè°¢è°¢ïŒâ<br />åŠå€ïŒé¶è¡è¿ç±»æ¯èŸææççœç«ç»åžžè¿è¡å°åºèåŽçå±èœãåŠæäœ å¹³æ¶åªåšæäžªç¹å®çåœå®¶äœ¿çšä»ä»¬çæå¡ïŒä»äœäº å¶ä»åœå®¶çåºå£èç¹è¿è¡è®¿é®æ¶äœ çèŽŠå·å¯èœå°±äŒè¢«å»ç»ãåŠæ æ³è¿æ¥ onion æå¡ïŒè¯·åé <a href=\"http://127.0.0.1:5000/#onionservices-3\">æ æ³è¿æ¥ x.onionïŒ</a></p>" + "description": "<p class=\\\"mb-3\\\">äžèœè®¿é®äœ æ³èŠççœç«çæ¯éæŸå¢ïŒæäºçœç«å±èœäº Tor å äžºä»ä»¬æ æ³åèŸšåºæ®é Tor çšæ·åæºåšäººçåºå«ãæ ¹æ®è¿å»çç»éªïŒæ³èŠè®©çœç«è§£å°æ¥èª Tor çè®¿é®æææçæ¹æ³æ¯ç±çšæ·çŽæ¥èç³»çœç«ç®¡çåãä¹è®žè¿æ ·çæ¶æ¯å°±å¯ä»¥æåïŒ<br />âåšïŒåšçš Tor Browser çæ¶ååç°äœ ççœç« xyz.com äžåè®žæ¥èª Tor çè®¿é®ïŒåžæäœ å¯ä»¥éæ°èèè¿äžªå³å®ãåšçåå°åŸå€äººéœåšäœ¿çš Tor æ¥ä¿æ€éç§åå¯¹æå®¡æ¥ïŒå±èœ Tor çåæ¶äœ ä¹å±èœäºåŒºæåœå®¶äžæ³èªç±è®¿é®äºèçœççšæ·ãéèŠéèèªå·±çè®°èåæ£äžŸèãæ³èº²é¿çœç»è·èžªçç ç©¶èåæ®éçšæ·ãè¯·ç«åšæ¯æåšçº¿éç§åçœç»èªç±çç«åºäžïŒåè®ž Tor çšæ·è®¿é® xyz.comïŒè°¢è°¢ïŒâ<br />åŠå€ïŒé¶è¡è¿ç±»æ¯èŸææççœç«ç»åžžè¿è¡å°åºèåŽçå±èœãåŠæäœ å¹³æ¶åªåšæäžªç¹å®çåœå®¶äœ¿çšä»ä»¬çæå¡ïŒä»å ¶ä»åœå®¶è¿è¡è®¿é®æ¶äœ çèŽŠå·å¯èœå°±äŒè¢«å»ç»ãåŠæ æ³è¿æ¥ onion æå¡ïŒè¯·åé <a href=\\\"http://127.0.0.1:5000/#onionservices-3\\\">æ æ³è¿æ¥ x.onionïŒ</a></p>" }, "censorship-3": { "id": "#å®¡æ¥-3", @@ -27,7 +27,7 @@ "id": "#å®¡æ¥-5", "control": "å®¡æ¥-5", "title": "æ æ³è¿æ¥å° TorïŒäœæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", - "description": "<p class=\"mb-3\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥</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\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</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\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæ šçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§æ¥å¿éè¯¯#3: TLSæ¡æå€±èŽ¥</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\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor äžäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5> åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯</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. \nToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœãè¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ã</code></pre></p><p class=\"mb-3\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" + "description": "<p class=\\\"mb-3\\\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥</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\\\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</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\\\">åŠææšçè§è¿äºæç€ºåº ç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§æ¥å¿éè¯¯#3: TLSæ¡æå€±èŽ¥</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\\\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor ä žäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5> åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯</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. \\nToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœãè¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ã</code></pre></p><p class=\\\"mb-3\\\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" }, "censorship-6": { "id": "#å®¡æ¥-6",

1 0

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

21 Apr '18

commit 87ddaff4617eeb6b129335e162d1ed9a0b0e8d59 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Apr 21 04:49:45 2018 +0000 Update translations for support-censorship --- zh_CN.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh_CN.json b/zh_CN.json index d681ecd8e..77e144e42 100644 --- a/zh_CN.json +++ b/zh_CN.json @@ -9,7 +9,7 @@ "id": "#å®¡æ¥-2", "control": "å®¡æ¥-2", "title": "ææç±ççœç«å±èœæ¥èª Tor çè®¿é®ã", - "description": "<p class=\"mb-3\">Sorry to hear that you can't visit the website you wanted! Sometimes websites will block Tor users because they can't tell the difference between the average Tor user and automated traffic. The best success we've had in getting sites to unblock Tor users is getting users to contact the site administrators directly. Something like this might do the trick:<br />\"Hi! I tried to access your site xyz.com while using Tor Browser and discovered that you don't allow Tor users to access your site. I urge you to reconsider this decision; Tor is used by people all over the world to protect their privacy and fight censorship. By blocking Tor users, you are likely blocking people in repressive countries who want to use a free internet, journalists and researchers who want to protect themselves from discovery, whistleblowers, activists, and ordinary people who want to opt out of invasive third party tracking. Please take a strong stance in favor of digital priv acy and internet freedom, and allow Tor users access to xyz.com. Thank you.\"<br />In the case of banks, and other sensitive websites, it is also common to see geography-based blocking (if a bank knows you generally access their services from one country, and suddenly you are connecting from an exit relay on the other side of the world, your account may be locked or suspended). If you are unable to connect to an onion service, please see <a href=\"#onionservices-3\">I cannot reach X.onion!</a></p>" + "description": "<p class=\\\"mb-3\\\">äžèœè®¿é®äœ æ³èŠççœç«çæ¯éæŸå¢ïŒæäºçœç«å±èœäº Tor å äžºä»ä»¬æ æ³åèŸšåºæ®é Tor çšæ·åæºåšäººçåºå«ãæ ¹æ®è¿å»çç»éªïŒæ³èŠè®©çœç«è§£å°æ¥èª Tor çè®¿é®æææçæ¹æ³æ¯ç±çšæ·çŽæ¥èç³»çœç«ç®¡çåãä¹è®žè¿æ ·çæ¶æ¯å°±å¯ä»¥æåïŒ<br />âåšïŒåšçš Tor Browser çæ¶ååç°äœ ççœç« xyz.com äžåè®žæ¥èª Tor çè®¿é®ïŒåžæäœ å¯ä»¥éæ°èèè¿äžªå³å®ãåšçåå°åŸå€äººéœåšäœ¿çš Tor æ¥ä¿æ€éç§åå¯¹æå®¡æ¥ïŒå±èœ Tor çåæ¶äœ ä¹å±èœäºåŒºæåœå®¶äžæ³èªç±è®¿é®äºèçœççšæ·ãéèŠéèèªå·±çè®°èåæ£äžŸèãæ³èº²é¿çœç»è·èžªçç ç©¶èåæ®éçšæ·ãè¯·ç«åšæ¯æåšçº¿éç§åçœç»èªç±çç«åºäžïŒåè®ž Tor çšæ·è®¿é® xyz.comïŒè°¢è°¢ïŒâ<br />åŠå€ïŒé¶è¡è¿ç±»æ¯èŸææççœç«ç»åžžè¿è¡å°åºèåŽçå±èœãåŠæäœ å¹³æ¶åªåšæäžªç¹å®çåœå®¶äœ¿çšä»ä»¬çæå¡ïŒä»å ¶ä»åœå®¶è¿è¡è®¿é®æ¶äœ çèŽŠå·å¯èœå°±äŒè¢«å»ç»ãåŠæ æ³è¿æ¥ onion æå¡ïŒè¯·åé <a href=\\\"http://127.0.0.1:5000/#onionservices-3\\\">æ æ³è¿æ¥ x.onionïŒ</a></p>" }, "censorship-3": { "id": "#å®¡æ¥-3", @@ -27,7 +27,7 @@ "id": "#å®¡æ¥-5", "control": "å®¡æ¥-5", "title": "æ æ³è¿æ¥å° TorïŒäœæäžç¥éåçäºä»ä¹ä»ä¹éè¯¯ã", - "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\\\">åŠææšçè¿æ¥åºç°é®é¢ïŒè¯·éæ©âå€å¶Toræ¥å¿å°åªèŽŽæ¿âéé¡¹ãç¶åç²èŽŽToræ¥å¿å°ææ¬æä»¶æèå¶ä»ææ¡£æ ŒåŒãæšåºè¯¥èœå€åšç²èŽŽçToræ¥å¿äžåç°è¿äºåžžè§é®é¢ïŒè¯·åšToræ¥å¿éå¯»æŸåŠäžæç€ºçéè¯¯ïŒ:</p><h5> åžžè§éè¯¯#1: ä»£çè¿æ¥å€±èŽ¥</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\\\"> åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšè¿æ¥SOCKSä»£çå€±èŽ¥äºãåŠææšçç³»ç»è®Ÿçœ®éèŠäžäžªSOCKSä»£ç, è¯·ä¿è¯æšæ£ç¡®çèŸå¥äºå³äºè¿äžªä»£ççéçœ®ã åŠææšçç³»ç»äžéèŠä»£çïŒæèæšäžæ¢è¯å®ïŒè¯·å°è¯çŽæ¥è¿æ¥Torçœç»ã<p><h5>åžžè§éè¯¯ #2: æ æ³è¿æ¥å°äžç»§</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\\\">åŠææšçè§è¿äºæç€ºåº ç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçTorè¿æ¥ Torçœç»äžçç¬¬äžäžªèç¹å€±èŽ¥äºãè¿å¯èœæå³çæšå€äºè¢«çç®¡ççœç»ä¹äžãè¯·å°è¯éè¿çœæ¡¥è¿æ¥ïŒè¿åºè¯¥èœè§£å³æšçé®é¢ã</p><h5>åžžè§æ¥å¿éè¯¯#3: TLSæ¡æå€±èŽ¥</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\\\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çTor ä žäžç»§ç®åœæäŸæå¡åšçTLSæ¡æå€±èŽ¥äºã äœ¿çšçœæ¡¥åºè¯¥èœè§£å³è¿äžªé®é¢</p><h5> åžžè§éè¯¯#4: æ¶éŽè®Ÿçœ®éè¯¯</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. \\nToréèŠäžäžªåç¡®çæ¶éŽæ¥ç»Žæå®çè¿äœãè¯·æ£æ¥æšçæ¶éŽïŒæ¶åºä»¥åæ¥æè®Ÿçœ®ã</code></pre></p><p class=\\\"mb-3\\\">åŠææšçè§è¿äºæç€ºåºç°åšæšçæ¥å¿éé¢ïŒè¿æå³çæšçç³»ç»æ¶éŽè®Ÿçœ®éè¯¯ãè¯·ç¡®è®€æšçæ¶éŽè®Ÿçœ®æ¯æ£ç¡®çïŒåæ¬æ£ç¡®çæ¶åºãç¶åéæ°å¯åšTorã </p>" }, "censorship-6": { "id": "#å®¡æ¥-6",

1 0

[translation/https_everywhere_completed] Update translations for https_everywhere_completed
by translation＠torproject.org 21 Apr '18

21 Apr '18

commit a6a1e06c5e0facd7191dadfa2523bf1686acaa79 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Apr 21 04:45:39 2018 +0000 Update translations for https_everywhere_completed --- zh_CN/https-everywhere.dtd | 1 + 1 file changed, 1 insertion(+) diff --git a/zh_CN/https-everywhere.dtd b/zh_CN/https-everywhere.dtd index 1d908e38d..5865a45e6 100644 --- a/zh_CN/https-everywhere.dtd +++ b/zh_CN/https-everywhere.dtd @@ -17,6 +17,7 @@ <!ENTITY https-everywhere.options.importSettings "导入设置"> <!ENTITY https-everywhere.options.import "导入"> <!ENTITY https-everywhere.options.enableMixedRulesets "启用混合内容规则集"> +<!ENTITY https-everywhere.options.showDevtoolsTab "显示开发者工具栏"> <!ENTITY https-everywhere.options.autoUpdateRulesets "自动更新规则集"> <!ENTITY https-everywhere.options.imported "您的设置已导入。">

1 0

[translation/https_everywhere] Update translations for https_everywhere
by translation＠torproject.org 21 Apr '18

21 Apr '18

commit 6a970cfbe58790019ed0a781c45a83154b30c225 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Apr 21 04:45:30 2018 +0000 Update translations for https_everywhere --- zh_CN/https-everywhere.dtd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh_CN/https-everywhere.dtd b/zh_CN/https-everywhere.dtd index 95935b903..5865a45e6 100644 --- a/zh_CN/https-everywhere.dtd +++ b/zh_CN/https-everywhere.dtd @@ -2,7 +2,7 @@ <!ENTITY https-everywhere.about.ext_name "HTTPS Everywhere"> <!ENTITY https-everywhere.about.ext_description "加密网络浏览，自动使用 HTTPS 连接访问站点，更加安全。"> <!ENTITY https-everywhere.about.version "版本"> -<!ENTITY https-everywhere.about.rulesets_version "Rulesets version for"> +<!ENTITY https-everywhere.about.rulesets_version "规则集的版本对于"> <!ENTITY https-everywhere.about.add_new_rule "添加新规则"> <!ENTITY https-everywhere.menu.donate_eff_imperative "捐助电子前线基金会 (EFF)"> @@ -17,7 +17,7 @@ <!ENTITY https-everywhere.options.importSettings "导入设置"> <!ENTITY https-everywhere.options.import "导入"> <!ENTITY https-everywhere.options.enableMixedRulesets "启用混合内容规则集"> -<!ENTITY https-everywhere.options.showDevtoolsTab "Show Devtools tab"> +<!ENTITY https-everywhere.options.showDevtoolsTab "显示开发者工具栏"> <!ENTITY https-everywhere.options.autoUpdateRulesets "自动更新规则集"> <!ENTITY https-everywhere.options.imported "您的设置已导入。">

1 0

[obfs4/master] fixup! Bug 24793: Send the correct authorization HTTP header for basic auth.
by yawning＠torproject.org 21 Apr '18

21 Apr '18

commit e3d4c5308d266ee267aefa7b9aa586107b812276 Author: Yawning Angel <yawning(a)schwanenlied.me> Date: Sat Apr 21 03:10:33 2018 +0000 fixup! Bug 24793: Send the correct authorization HTTP header for basic auth. --- ChangeLog | 1 + 1 file changed, 1 insertion(+) diff --git a/ChangeLog b/ChangeLog index 8c89813..3a4a178 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,4 +1,5 @@ Changes in version 0.0.8 - UNRELEASED: + - Bug 24793: Send the correct authorization HTTP header for basic auth. Changes in version 0.0.7 - 2016-11-15: - Support configuring the obfs4 IAT parameter as the sole

1 0

[obfs4/master] (meek_lite) Explicitly set Content-Length to zero when there is no data to send.
by yawning＠torproject.org 21 Apr '18

21 Apr '18

commit 89c21805c212bcc2f5a0c4ffdadf424cbff1c7c9 Author: Yawning Angel <yawning(a)schwanenlied.me> Date: Sat Apr 21 03:11:26 2018 +0000 (meek_lite) Explicitly set Content-Length to zero when there is no data to send. https://gitweb.torproject.org/pluggable-transports/meek.git/commit/?h=0.28&… --- ChangeLog | 2 ++ transports/meeklite/meek.go | 6 +++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 3a4a178..361ceb4 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,7 @@ Changes in version 0.0.8 - UNRELEASED: - Bug 24793: Send the correct authorization HTTP header for basic auth. + - (meek_lite) Explicitly set Content-Length to zero when there is no data + to send. Changes in version 0.0.7 - 2016-11-15: - Support configuring the obfs4 IAT parameter as the sole diff --git a/transports/meeklite/meek.go b/transports/meeklite/meek.go index f0d29db..e068b68 100644 --- a/transports/meeklite/meek.go +++ b/transports/meeklite/meek.go @@ -231,7 +231,11 @@ func (c *meekConn) roundTrip(sndBuf []byte) (recvBuf []byte, err error) { if c.args.front != "" { url.Host = c.args.front } - req, err = http.NewRequest("POST", url.String(), bytes.NewReader(sndBuf)) + var body io.Reader + if len(sndBuf) > 0 { + body = bytes.NewReader(sndBuf) + } + req, err = http.NewRequest("POST", url.String(), body) if err != nil { return nil, err }

1 0

[webwml/master] Remove old key from the signing-keys page
by boklm＠torproject.org 20 Apr '18

20 Apr '18

commit b482df8dc1a92039e65c8d1324e4340d0119adf4 Author: Nicolas Vigier <boklm(a)torproject.org> Date: Sat Apr 21 00:05:50 2018 +0200 Remove old key from the signing-keys page --- docs/en/signing-keys.wml | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/en/signing-keys.wml b/docs/en/signing-keys.wml index 37de1c59..e05c1fbf 100644 --- a/docs/en/signing-keys.wml +++ b/docs/en/signing-keys.wml @@ -30,7 +30,7 @@ <li>David Goulet (0x42E86A2A11F48D36) signs Torsocks releases.</li> <li>Sukhbir Singh (0xB01C8B006DA77FAA) signs Tor Messenger and TorBirdy releases.</li> <li>Other developers include Peter Palfrader (0xC82E0039, or its - subkey 0xE1DEC577) and Jacob Appelbaum (0xFA7F0E44D487F03F).</li> + subkey 0xE1DEC577).</li> </ul> The fingerprints for the keys should be: @@ -126,12 +126,6 @@ uid [ full ] Arthur Edelstein <arthuredelstein(a)gmail.com> sub 2048R/3306E88D27211E0B 2014-12-10 - pub 4096R/FA7F0E44D487F03F 2014-06-27 [expires: 2024-06-24] - Key fingerprint = D6A9 48CF 297F 7539 30B4 756A FA7F 0E44 D487 F03F - uid Jacob Appelbaum <jacob(a)torproject.org> - sub 3072R/36A3F38A 2015-07-01 [expires: 2016-06-30] - sub 3072R/45EDE84B 2015-07-01 [expires: 2016-06-30] - pub 4096R/0x4E2C6E8793298290 2014-12-15 [expires: 2020-08-24] Key fingerprint = EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87 9329 8290 uid Tor Browser Developers (signing key) <torbrowser(a)torproject.org>

1 0

[webwml/master] Add new Tor Browser version: 8.0a6
by boklm＠torproject.org 20 Apr '18

20 Apr '18

commit e595e241af12366c5039843e109d47180f9b270d Author: Nicolas Vigier <boklm(a)torproject.org> Date: Sat Apr 21 00:12:30 2018 +0200 Add new Tor Browser version: 8.0a6 --- include/versions.wmi | 4 ++-- projects/torbrowser/RecommendedTBBVersions | 6 +++++- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/include/versions.wmi b/include/versions.wmi index a4c56ebd..4acd207b 100644 --- a/include/versions.wmi +++ b/include/versions.wmi @@ -22,8 +22,8 @@ <define-tag package-win32-stable whitespace=delete>../dist/torbrowser/<version-torbrowserbundle>/tor-win32-<version-win32-stable>.zip</define-tag> # *** tor browser beta/alpha *** -<define-tag version-torbrowserbundlebeta-all whitespace=delete>8.0a5</define-tag> -<define-tag releasedate-torbrowserbundlebeta-all whitespace=delete>2018-03-26</define-tag> +<define-tag version-torbrowserbundlebeta-all whitespace=delete>8.0a6</define-tag> +<define-tag releasedate-torbrowserbundlebeta-all whitespace=delete>2018-04-21</define-tag> <define-tag version-torbrowsersandboxlinux whitespace=delete>0.0.16</define-tag> # If all platforms are on the same version, you only need to update diff --git a/projects/torbrowser/RecommendedTBBVersions b/projects/torbrowser/RecommendedTBBVersions index c98e4243..2fefb90c 100644 --- a/projects/torbrowser/RecommendedTBBVersions +++ b/projects/torbrowser/RecommendedTBBVersions @@ -6,5 +6,9 @@ "8.0a5", "8.0a5-MacOS", "8.0a5-Linux", -"8.0a5-Windows" +"8.0a5-Windows", +"8.0a6", +"8.0a6-MacOS", +"8.0a6-Linux", +"8.0a6-Windows" ]

1 0

[webwml/master] Bug 25846: Add Arthur's key to the signing-keys page
by boklm＠torproject.org 20 Apr '18

20 Apr '18

commit fc8852c5ab7a5a875e7636947b4b27d1d51a1a97 Author: Nicolas Vigier <boklm(a)torproject.org> Date: Thu Apr 19 12:32:09 2018 +0200 Bug 25846: Add Arthur's key to the signing-keys page --- docs/en/signing-keys.wml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/en/signing-keys.wml b/docs/en/signing-keys.wml index 8a868aed..37de1c59 100644 --- a/docs/en/signing-keys.wml +++ b/docs/en/signing-keys.wml @@ -16,7 +16,8 @@ <ul> <li>The Tor Browser Developers (0x93298290), Mike Perry (0x0E3A92E4), Georg Koppen (0x4B7C3223), - Nicolas Vigier (0xD0220E4B) and Linus Nordberg (0x23291265) + Nicolas Vigier (0xD0220E4B), Linus Nordberg (0x23291265) + and Arthur Edelstein (0xD752F538C0D38C3A) sign the Tor Browser releases.</li> <li>Roger Dingledine (0x28988BF5 and 0x19F78451) or Nick Mathewson (0xFE43009C4607B1FB with signing key 0x6AFEE6D49E92B601) @@ -120,6 +121,11 @@ Key fingerprint = 4A90 646C 0BAE D9D4 56AB 3111 E5B8 1856 D022 0E4B uid Nicolas Vigier (TBB Builds Signing Key) <boklm(a)torproject.org> + pub 2048R/D752F538C0D38C3A 2014-12-10 + Key fingerprint = 20B2 4CEF E6AF D615 0B6A 6F18 D752 F538 C0D3 8C3A + uid [ full ] Arthur Edelstein <arthuredelstein(a)gmail.com> + sub 2048R/3306E88D27211E0B 2014-12-10 + pub 4096R/FA7F0E44D487F03F 2014-06-27 [expires: 2024-06-24] Key fingerprint = D6A9 48CF 297F 7539 30B4 756A FA7F 0E44 D487 F03F uid Jacob Appelbaum <jacob(a)torproject.org>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits April 2018