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

[webwml/master] Change Onionoo links to point to new location (Fixes: #23802)
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit ffc651dff413db0ec78b4fb644b7b5800abb656c Author: Iain R. Learmonth <irl(a)fsfe.org> Date: Mon Oct 9 21:14:46 2017 +0100 Change Onionoo links to point to new location (Fixes: #23802) Signed-off-by: hiro <hiro(a)torproject.org> --- getinvolved/en/volunteer.wml | 2 +- projects/en/projects.wml | 4 ++-- projects/en/sidenav.wmi | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index 100d5ba7..7981a08e 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -575,7 +575,7 @@ meetings around the world.</li> </p> <a id="project-onionoo"></a> - <h3><a href="https://onionoo.torproject.org/">Onionoo</a> (<a + <h3><a href="https://metrics.torproject.org/onionoo.html">Onionoo</a> (<a href="https://gitweb.torproject.org/onionoo.git">code</a>, <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…">bug tracker</a>)</h3> diff --git a/projects/en/projects.wml b/projects/en/projects.wml index d6fd6aba..f8cec800 100644 --- a/projects/en/projects.wml +++ b/projects/en/projects.wml @@ -64,11 +64,11 @@ instead of the actual Tor traffic.</p> </div> <div class="projectbox"> -<a href="https://onionoo.torproject.org/"><img class="icon" +<a href="https://metrics.torproject.org/onionoo.html"><img class="icon" src="$(IMGROOT)/icon-TorStatus.jpg" alt="Onionoo Icon" width="75" height="75"></a> <div class="projectdesc"><div class="name"><a -href="https://onionoo.torproject.org/">Onionoo</a></div> +href="https://metrics.torproject.org/onionoo.html">Onionoo</a></div> <p>Web-based protocol to learn about currently running Tor relays and bridges.</p> </div></div> diff --git a/projects/en/sidenav.wmi b/projects/en/sidenav.wmi index 63dbcd39..f80ab167 100644 --- a/projects/en/sidenav.wmi +++ b/projects/en/sidenav.wmi @@ -41,7 +41,7 @@ {'url' => 'https://trac.torproject.org/projects/tor/wiki/torbirdy', 'txt' => 'TorBirdy', }, - {'url' => 'https://onionoo.torproject.org/', + {'url' => 'https://metrics.torproject.org/onionoo.html', 'txt' => 'Onionoo', }, {'url' => 'https://metrics.torproject.org/',

1 0

[webwml/master] Bug 23917: Update gk's GPG subbkeys on website
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 21cc591e2edc1785b12788f90fadd3182da054f6 Author: Georg Koppen <gk(a)torproject.org> Date: Fri Oct 20 08:24:02 2017 +0000 Bug 23917: Update gk's GPG subbkeys on website Signed-off-by: hiro <hiro(a)torproject.org> --- docs/en/signing-keys.wml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/signing-keys.wml b/docs/en/signing-keys.wml index 4b8e6d45..8a868aed 100644 --- a/docs/en/signing-keys.wml +++ b/docs/en/signing-keys.wml @@ -110,11 +110,11 @@ uid Linus Nordberg <linus(a)torproject.org> sub 4096R/B5F7D1B1 2016-04-14 [expires: 2017-04-14] - pub 4096R/4B7C3223 2013-07-30 + pub rsa4096/0x94373AA94B7C3223 2013-07-30 Key fingerprint = 35CD 74C2 4A9B 15A1 9E1A 81A1 9437 3AA9 4B7C 3223 uid Georg Koppen <gk(a)torproject.org> - sub 4096R/0x2F7477373D6B000D 2016-08-01 [expires: 2017-09-11] - sub 4096R/0xAA602CC00C257CF7 2016-08-01 [expires: 2017-09-11] + sub rsa4096/0x5778071EE2DE675B 2017-09-11 [expires: 2018-09-11] + sub rsa4096/0x72E841BB93148AD2 2017-09-11 [expires: 2018-09-11] pub 4096R/D0220E4B 2014-03-19 Key fingerprint = 4A90 646C 0BAE D9D4 56AB 3111 E5B8 1856 D022 0E4B

1 0

[webwml/master] Use English "singular they" where appropriate
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 536ce69287ce17e09938623fcbb2227fda1dc2ff Author: Ingo Blechschmidt <iblech(a)speicherleck.de> Date: Sun Dec 10 14:20:39 2017 +0100 Use English "singular they" where appropriate Signed-off-by: hiro <hiro(a)torproject.org> --- docs/en/faq-abuse.wml | 4 ++-- docs/en/faq.wml | 16 ++++++++-------- docs/en/onion-services.wml | 4 ++-- 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/en/faq-abuse.wml b/docs/en/faq-abuse.wml index d916bf97..c9cac5ba 100644 --- a/docs/en/faq-abuse.wml +++ b/docs/en/faq-abuse.wml @@ -204,8 +204,8 @@ using technology?</a></li> <p>But the real answer is to implement application-level auth systems, to let in well-behaving users and keep out badly-behaving users. This - needs to be based on some property of the human (such as a password he - knows), not some property of the way his packets are transported. </p> + needs to be based on some property of the human (such as a password they + know), not some property of the way their packets are transported. </p> <p>Of course, not all IRC networks are trying to ban Tor nodes. After all, quite a few people use Tor to IRC in privacy in order to carry diff --git a/docs/en/faq.wml b/docs/en/faq.wml index 4a63ccb3..0a9b38ee 100644 --- a/docs/en/faq.wml +++ b/docs/en/faq.wml @@ -2453,8 +2453,8 @@ exit policies are propagated to Tor clients via the directory, so clients will automatically avoid picking exit relays that would refuse to exit to their intended destination. This way each relay can decide - the services, hosts, and networks he wants to allow connections to, - based on abuse potential and his own situation. Read the FAQ entry + the services, hosts, and networks it wants to allow connections to, + based on abuse potential and its own situation. Read the FAQ entry on <a href="<page docs/faq-abuse>#TypicalAbuses">issues you might encounter</a> @@ -2931,14 +2931,14 @@ Yes, you do get better anonymity against some attacks. </p> <p> The simplest example is an attacker who owns a small number of Tor relays. -He will see a connection from you, but he won't be able to know whether +They will see a connection from you, but they won't be able to know whether the connection originated at your computer or was relayed from somebody else. </p> <p> There are some cases where it doesn't seem to help: if an attacker can -watch all of your incoming and outgoing traffic, then it's easy for him +watch all of your incoming and outgoing traffic, then it's easy for them to learn which connections were relayed and which started at you. (In -this case he still doesn't know your destinations unless he is watching +this case they still don't know your destinations unless they are watching them too, but you're no better off than if you were an ordinary client.) </p> <p> @@ -2948,7 +2948,7 @@ signal to an attacker that you place a high value on your anonymity. Second, there are some more esoteric attacks that are not as well-understood or well-tested that involve making use of the knowledge that you're running a relay -- for example, an attacker may be able to -"observe" whether you're sending traffic even if he can't actually watch +"observe" whether you're sending traffic even if they can't actually watch your network, by relaying traffic through your Tor relay and noticing changes in traffic timing. </p> @@ -3475,7 +3475,7 @@ keys, locations, exit policies, and so on. So unless the adversary can control a majority of the directory authorities (as of 2012 there are 8 - directory authorities), he can't trick the Tor client into using + directory authorities), they can't trick the Tor client into using other Tor relays. </p> @@ -4213,7 +4213,7 @@ only solution is to have no opinion. Like all anonymous communication networks that are fast enough for web browsing, Tor is vulnerable to statistical "traffic confirmation" attacks, where the adversary watches traffic at both ends of a circuit - and confirms his guess that they're communicating. It would be really + and confirms their guess that those endpoints are communicating. It would be really nice if we could use cover traffic to confuse this attack. But there are three problems here: </p> diff --git a/docs/en/onion-services.wml b/docs/en/onion-services.wml index a73ff7d3..c35b76c3 100644 --- a/docs/en/onion-services.wml +++ b/docs/en/onion-services.wml @@ -107,9 +107,9 @@ the same set of <a href="<wikifaq>#Whatsthisaboutentryguardformerlyknownashelpernodes">entry guards</a> when creating new circuits. Otherwise an attacker - could run his own relay and force an onion service to create an arbitrary + could run their own relay and force an onion service to create an arbitrary number of circuits in the hope that the corrupt relay is picked as entry - node and he learns the onion server's IP address via timing analysis. This + node and they learn the onion server's IP address via timing analysis. This attack was described by Øverlier and Syverson in their paper titled <a href="http://freehaven.net/anonbib/#hs-attack06">Locating Hidden Servers</a>.

1 0

[webwml/master] Updates all Relay Search URLs to new location (Fixes: #25286)
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 7390385a3e746535758c45a5a7a8943ecac7872b Author: Iain R. Learmonth <irl(a)fsfe.org> Date: Sat Feb 17 13:41:06 2018 +0000 Updates all Relay Search URLs to new location (Fixes: #25286) Signed-off-by: hiro <hiro(a)torproject.org> --- about/en/corepeople.wml | 4 ++-- docs/en/documentation.wml | 2 +- en/index.wml | 5 +++-- getinvolved/en/volunteer.wml | 2 +- 4 files changed, 7 insertions(+), 6 deletions(-) diff --git a/about/en/corepeople.wml b/about/en/corepeople.wml index cfa4f925..e3f3a46c 100644 --- a/about/en/corepeople.wml +++ b/about/en/corepeople.wml @@ -115,7 +115,7 @@ <div class="icon"><a href="https://db.torproject.org/fetchkey.cgi?fingerprint=67EF3966509986E96ACEE84E…"><img src="$(IMGROOT)/pgp-key.png" alt="pgp key" /></a></div> <div class="name"><a href="#hellais">Arturo Filastò</a></div> <div class="field"><b>IRC:</b> hellais</div> - <div class="description">Project leader for <a href="https://ooni.torproject.org/">OONI</a>, has helped with <a href="http://tor2web.org/">tor2web</a>, wrote Atlas which later became <a href="https://atlas.torproject.org/">Relay Search</a>, and helps improve security.</div> + <div class="description">Project leader for <a href="https://ooni.torproject.org/">OONI</a>, has helped with <a href="http://tor2web.org/">tor2web</a>, wrote Atlas which later became <a href="https://metrics.torproject.org/rs.html">Relay Search</a>, and helps improve security.</div> </td> </tr> @@ -271,7 +271,7 @@ <div class="icon"><a href="https://db.torproject.org/fetchkey.cgi?fingerprint=A8F7BA5041E133339CBA1696…"><img src="$(IMGROOT)/pgp-key.png" alt="pgp key" /></a></div> <div class="name"><a href="#irl">Iain Learmonth</a></div> <div class="field"><b>IRC:</b> irl</div> - <div class="description"><a href="https://metrics.torproject.org">Metrics team member</a> and maintainer of <a href="https://atlas.torproject.org/">Relay Search</a>.</div> + <div class="description"><a href="https://metrics.torproject.org">Metrics team member</a> and maintainer of <a href="https://metrics.torproject.org/rs.html">Relay Search</a>.</div> </td> <td> diff --git a/docs/en/documentation.wml b/docs/en/documentation.wml index 1aa4e0ce..edfd4780 100644 --- a/docs/en/documentation.wml +++ b/docs/en/documentation.wml @@ -224,7 +224,7 @@ <li><a href="https://check.torproject.org/">The Tor detector</a> tries to guess if you're using Tor or not.</li> <li>Check out Tor network status information using <a - href="https://atlas.torproject.org/">Relay Search</a>. + href="https://metrics.torproject.org/rs.html">Relay Search</a>. Remember that these lists may not be as accurate as what your Tor client uses, because your client fetches its own directory information and examines it locally.</li> diff --git a/en/index.wml b/en/index.wml index 0a7cba7e..fc675683 100644 --- a/en/index.wml +++ b/en/index.wml @@ -107,9 +107,10 @@ --> <td> <div class="project"> - <a href="https://atlas.torproject.org/"><img + <a href="https://metrics.torproject.org/rs.html"><img src="$(IMGROOT)/icon-TorStatus.jpg" alt="Atlas Icon"></a> - <h3><a href="https://atlas.torproject.org/">Relay Search</a></h3> + <h3><a href="https://metrics.torproject.org/rs.html">Relay + Search</a></h3> <p>Site providing an overview of the Tor network.</p> </div> </td> diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml index 5ece2ca8..100d5ba7 100644 --- a/getinvolved/en/volunteer.wml +++ b/getinvolved/en/volunteer.wml @@ -555,7 +555,7 @@ meetings around the world.</li> </p> <a id="project-atlas"></a> - <h3><a href="https://atlas.torproject.org/">Relay Search</a> (<a + <h3><a href="https://metrics.torproject.org/rs.html">Relay Search</a> (<a href="https://gitweb.torproject.org/atlas.git">code</a>)</h3> <p>

1 0

[webwml/master] FAQ (relay section): increase min. bw from 2 to 8 MBit/s and add bridge info
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 660b94dc904c73bdbfa4884ad02f5f488531f7c6 Author: nusenu <nusenu-github(a)riseup.net> Date: Sat Feb 10 13:11:47 2018 +0000 FAQ (relay section): increase min. bw from 2 to 8 MBit/s and add bridge info --- docs/en/faq.wml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/en/faq.wml b/docs/en/faq.wml index b15de6f2..9165a7cd 100644 --- a/docs/en/faq.wml +++ b/docs/en/faq.wml @@ -2034,9 +2034,11 @@ from the source code release tor-0.2.4.16-rc is: run a relay?</a></h3> <p> We're looking for people with reasonably reliable Internet connections, - that have at least 250 kilobytes/second each way. If that's you, please - consider <a href="https://www.torproject.org/docs/tor-relay-debian">helping - out</a>. + that have at least 1 MByte/second (that is 8 MBit/second) available bandwidth each way. If that's you, please + consider <a href="<wiki>TorRelayGuide">running a Tor relay</a>. + </p> + <p> + Even if you do not have at least 8 MBit/s of available bandwidth you can still help the Tor network by running a <a href="<page docs/pluggable-transports>#operator">Tor bridge with obfs4 support</a>. In that case you should have at least 1 MBit/s of available bandwidth. </p> <hr>

1 0

[webwml/master] FAQ (relay section): dynamic IPs are covered in a dedicated answer already
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 881b6370b5419794a7e4d72f78027be072c2425a Author: nusenu <nusenu-github(a)riseup.net> Date: Sat Feb 10 13:58:10 2018 +0000 FAQ (relay section): dynamic IPs are covered in a dedicated answer already --- docs/en/faq.wml | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/en/faq.wml b/docs/en/faq.wml index bef1beed..ba7d9854 100644 --- a/docs/en/faq.wml +++ b/docs/en/faq.wml @@ -2160,9 +2160,6 @@ relays. sure it's not too often, since connections using the relay when it disconnects will break. </li> - <li>We can handle relays with dynamic IPs just fine — simply - leave the Address config option blank, and Tor will try to guess. - </li> <li>If your relay is behind a NAT and it doesn't know its public IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port forwarding. Forwarding TCP connections is system dependent but

1 0

[webwml/master] FAQ (relay section): new entry: most wanted relay type
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit fbd1ac8776c556a94be2669a0f6c206b3e355c09 Author: nusenu <nusenu-github(a)riseup.net> Date: Sat Feb 10 13:55:07 2018 +0000 FAQ (relay section): new entry: most wanted relay type --- docs/en/faq.wml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/en/faq.wml b/docs/en/faq.wml index 9165a7cd..bef1beed 100644 --- a/docs/en/faq.wml +++ b/docs/en/faq.wml @@ -140,6 +140,7 @@ country) <li><a href="#HowDoIDecide">How do I decide if I should run a relay? </a></li> + <li><a href="#MostNeededRelayType">What type of relays are most needed?</a></li> <li><a href="#WhyIsntMyRelayBeingUsedMore">Why isn't my relay being used more?</a></li> <li><a href="#IDontHaveAStaticIP">I don't have a static IP.</a></li> @@ -2043,6 +2044,19 @@ from the source code release tor-0.2.4.16-rc is: <hr> + <a id="MostNeededRelayType"></a> + <h3><a class="anchor" href="#MostNeededRelayType">What type of relays are most needed?</a></h3> + <p> + <ul> + <li>The exit relay is the most needed relay type but it also comes with the highest legal exposure and risk (and you + should NOT run them from your home).</li> + <li>If you are looking to run a relay with minimal effort, fast guard relays are also very useful</li> + <li>followed by bridges.</li> + </ul> + </p> + + <hr> + <a id="WhyIsntMyRelayBeingUsedMore"></a> <h3><a class="anchor" href="#WhyIsntMyRelayBeingUsedMore">Why isn't my relay being used more?</a></h3>

1 0

[webwml/master] FAQ (relay section): put most relevant answer in this question at the beginning
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 8b81e16dc15de36ddea985d55a4324ec3afa69e8 Author: nusenu <nusenu-github(a)riseup.net> Date: Sat Feb 10 14:00:25 2018 +0000 FAQ (relay section): put most relevant answer in this question at the beginning --- docs/en/faq.wml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/en/faq.wml b/docs/en/faq.wml index ba7d9854..4dc00320 100644 --- a/docs/en/faq.wml +++ b/docs/en/faq.wml @@ -2136,6 +2136,11 @@ need to be?</a></h3> </p> <ul> + <li>It's fine if the relay goes offline sometimes. The directories + notice this quickly and stop advertising the relay. Just try to make + sure it's not too often, since connections using the relay when it + disconnects will break. + </li> <li>Tor has built-in support for <a href="#BandwidthShaping"> rate limiting</a>. Further, if you have a fast @@ -2155,11 +2160,6 @@ your relay, you can set it up to only allow connections to other Tor relays. </li> - <li>It's fine if the relay goes offline sometimes. The directories - notice this quickly and stop advertising the relay. Just try to make - sure it's not too often, since connections using the relay when it - disconnects will break. - </li> <li>If your relay is behind a NAT and it doesn't know its public IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port forwarding. Forwarding TCP connections is system dependent but

1 0

[webwml/master] FAQ (relay section): refrase static IP section into a question
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 60dd405a39149835a104429b811b56b1e3d388c2 Author: nusenu <nusenu-github(a)riseup.net> Date: Sat Feb 10 14:46:06 2018 +0000 FAQ (relay section): refrase static IP section into a question --- docs/en/faq.wml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/faq.wml b/docs/en/faq.wml index 6c113eb3..05eb799e 100644 --- a/docs/en/faq.wml +++ b/docs/en/faq.wml @@ -143,7 +143,7 @@ country) <li><a href="#MostNeededRelayType">What type of relays are most needed?</a></li> <li><a href="#WhyIsntMyRelayBeingUsedMore">Why isn't my relay being used more?</a></li> - <li><a href="#IDontHaveAStaticIP">I don't have a static IP.</a></li> + <li><a href="#IDontHaveAStaticIP">Can I run a Tor relay using a dynamic IP address?</a></li> <li><a href="#PortscannedMore">Why do I get portscanned more often when I run a Tor relay?</a></li> <li><a href="#HighCapacityConnection">How can I get Tor to fully @@ -2079,8 +2079,8 @@ from the source code release tor-0.2.4.16-rc is: <hr> <a id="IDontHaveAStaticIP"></a> - <h3><a class="anchor" href="#IDontHaveAStaticIP">I don't have a static - IP.</a></h3> + <h3><a class="anchor" href="#IDontHaveAStaticIP">Can I run a Tor relay using a + dynamic IP address?</a></h3> <p> Tor can handle relays with dynamic IP addresses just fine. Just leave

1 0

[webwml/master] FAQ (relay section): NAT is covered in its own section (this section is about stability)
by hiro＠torproject.org 02 Apr '18

02 Apr '18

commit 546a9e38e3785e3f0be6e0c7618559aa530454ae Author: nusenu <nusenu-github(a)riseup.net> Date: Sat Feb 10 14:41:19 2018 +0000 FAQ (relay section): NAT is covered in its own section (this section is about stability) --- docs/en/faq.wml | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/en/faq.wml b/docs/en/faq.wml index 0bd4eb5e..6c113eb3 100644 --- a/docs/en/faq.wml +++ b/docs/en/faq.wml @@ -2150,12 +2150,6 @@ your relay, you can set it up to only allow connections to other Tor relays. </li> - <li>If your relay is behind a NAT and it doesn't know its public - IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port - forwarding. Forwarding TCP connections is system dependent but - <a href="#BehindANAT">this FAQ entry</a> - offers some examples on how to do this. - </li> <li>Your relay will passively estimate and advertise its recent bandwidth capacity, so high-bandwidth relays will attract more users than

1 0