[tor-commits] [community/master] Make color header consistent
antonela at torproject.org
antonela at torproject.org
Thu Dec 5 11:55:02 UTC 2019
commit 276e27d951de5175315a62aa863a1f992dfbcc02
Author: Antonela <hola at antonela.me>
Date: Thu Dec 5 08:54:43 2019 -0300
Make color header consistent
Fix https://dip.torproject.org/torproject/web/community/issues/108
---
.../community-resources/bad-relays/contents.lr | 26 ++++++++++++----------
.../eff-tor-legal-faq/contents.lr | 4 +++-
.../tor-dmca-response/contents.lr | 2 ++
.../community-resources/good-bad-isps/contents.lr | 2 ++
.../community-resources/swag/contents.lr | 6 +++--
.../tor-abuse-templates/contents.lr | 2 ++
.../tor-exit-guidelines/contents.lr | 4 +++-
.../tor-relay-universities/contents.lr | 4 +++-
8 files changed, 33 insertions(+), 17 deletions(-)
diff --git a/content/relay-operations/community-resources/bad-relays/contents.lr b/content/relay-operations/community-resources/bad-relays/contents.lr
index 217730a..594eaf6 100644
--- a/content/relay-operations/community-resources/bad-relays/contents.lr
+++ b/content/relay-operations/community-resources/bad-relays/contents.lr
@@ -1,10 +1,12 @@
_model: page
---
+color: primary
+---
title: Bad relays
---
body:
-Ran into a misconfigured, malicious, or suspicious relay while using Tor? Please let us know by sending email to bad-relays AT lists DOT torproject DOT org! Many bad relays are caught thanks to our wider community, so many thanks for all your help and vigilance!
+Ran into a misconfigured, malicious, or suspicious relay while using Tor? Please let us know by sending email to bad-relays AT lists DOT torproject DOT org! Many bad relays are caught thanks to our wider community, so many thanks for all your help and vigilance!
### What is a bad relay?
@@ -12,16 +14,16 @@ A bad relay is one that either doesn't work properly or tampers with our users'
* Tampering with exit traffic in any way (including dropping accepted connections). This might be accidental (such as an anti-virus filter) or malicious (commonly SSLStrip, which replaces https:// links with http:// to snoop on traffic) or even intentional (such as layer 7 inspection for P2P traffic detection/mitigation).
* Running HSDirs that harvest and probe .onion addresses
- * Manipulating the DHT that is used for onion services, e.g., by positioning itself in the DHT.
+ * Manipulating the DHT that is used for onion services, e.g., by positioning itself in the DHT.
* Using a DNS provider that censors its results (such as some [OpenDNS](http://www.opendns.com) or Quad (9 9.9.9.9) configurations).
* Performing a [Sybil attack](https://en.wikipedia.org/wiki/Sybil_attack), which means flooding the network with new relays in an effort to deanonymize users. If you want to run multiple relays then that's great! But please be sure to set the [MyFamily parameter](https://www.torproject.org/docs/tor-manual.html.en#MyFamily).
- * Exit relays routing their exit traffic back into the tor network (not actually exiting any traffic)
-
+ * Exit relays routing their exit traffic back into the tor network (not actually exiting any traffic)
+
Also, if your relay is stolen or goes missing, please report it as well, so we can blacklist it in case whoever took it puts it back online.
-The following are currently permitted yet do have some discussion for prohibition (as such, they should not be reported at this time)...
+The following are currently permitted yet do have some discussion for prohibition (as such, they should not be reported at this time)...
- * Only allowing plain-text traffic (for instance, just port 80). There's no good reason to disallow its encrypted counterpart (like port 443), making these relays highly suspect for sniffing traffic. See [context](https://www.google.com/search?site:torproject.org+80+443+6667) and [spec](https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1969).
+ * Only allowing plain-text traffic (for instance, just port 80). There's no good reason to disallow its encrypted counterpart (like port 443), making these relays highly suspect for sniffing traffic. See [context](https://www.google.com/search?site:torproject.org+80+443+6667) and [spec](https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1969).
### How do I report a bad relay?
@@ -31,9 +33,9 @@ You can check which exit you are using at any time by visiting [tor check](https
1. The relay's IP address or fingerprint. The fingerprint is a forty-character hex string such as `203933ED4E55EF8A3C3518427D1A1ED6A4CC285E`.
2. What kind of behavior did you see?
- 3. Any additional information we'll need to reproduce the issue.
+ 3. Any additional information we'll need to reproduce the issue.
-However, if you need help with anything Tor-related, please contact the [help desk](https://www.torproject.org/about/contact) instead.
+However, if you need help with anything Tor-related, please contact the [help desk](https://www.torproject.org/about/contact) instead.
### What happens to bad relays?
@@ -43,19 +45,19 @@ We have thee types of flags we can apply:
* BadExit - Never used as an exit relay (for relays that appear to mess with exit traffic)
* Invalid - Never used unless AllowInvalidNodes is set (by default this only allows for middle and rendezvous usage)
- * Reject - Dropped from the consensus entirely
+ * Reject - Dropped from the consensus entirely
-Which we use depends on the severity of the issue, and if it can still be safely used in certain situations.
+Which we use depends on the severity of the issue, and if it can still be safely used in certain situations.
### My relays was given the BadExit flag. What's up?
-In just about all cases we're unable to contact the operator to resolve the issue, so if your relay has been flagged as a BadExit then please let us know (see above for contact info) so we can work together to fix the issue.
+In just about all cases we're unable to contact the operator to resolve the issue, so if your relay has been flagged as a BadExit then please let us know (see above for contact info) so we can work together to fix the issue.
### Do you actively look for bad relays?
Yes. For our automated issue detection see [exitmap](http://www.cs.kau.se/philwint/spoiled_onions/) and [sybilhunter](https://gitweb.torproject.org/user/phw/sybilhunter.git/).
-Other monitors include [tortunnel](http://www.thoughtcrime.org/software/tortunnel/), [SoaT](https://gitweb.torproject.org/torflow.git/blob/HEAD:/NetworkScanners/ExitAuthority/README.ExitScanning), [torscanner](https://code.google.com/p/torscanner/), and [DetecTor](http://detector.io/DetecTor.html).
+Other monitors include [tortunnel](http://www.thoughtcrime.org/software/tortunnel/), [SoaT](https://gitweb.torproject.org/torflow.git/blob/HEAD:/NetworkScanners/ExitAuthority/README.ExitScanning), [torscanner](https://code.google.com/p/torscanner/), and [DetecTor](http://detector.io/DetecTor.html).
---
diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr
index 0875d86..acc857c 100644
--- a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr
+++ b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: The Legal FAQ for Tor Relay Operators
---
body:
@@ -62,7 +64,7 @@ Of course, you should avoid keeping any sensitive or personal information on the
The Tor Project [suggests](https://blog.torproject.org/blog/tips-running-exit-node) the following ways to let others know that you're running an exit relay:
- * Set up a reverse DNS name for the IP address that makes clear that the computer is an exit relay.
+ * Set up a reverse DNS name for the IP address that makes clear that the computer is an exit relay.
* Set up a notice like [this](https://blog.torproject.org/blog/tips-running-exit-node) to explain that you're running an exit relay that's part of the Tor network.
* If possible, get an [ARIN](https://www.arin.net/) registration for your exit relay that displays contact information for you, not your ISP. This way, you'll receive any abuse complaints and can respond to them directly. Otherwise, try to ensure that your ISP forwards abuse complaints that it receives to you.
diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr
index e844d39..1bbccb8 100644
--- a/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr
+++ b/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: Response template for Tor relay operator to ISP
---
body:
diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr
index 4100d18..4dab46e 100644
--- a/content/relay-operations/community-resources/good-bad-isps/contents.lr
+++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: Good Bad ISPs
---
body:
diff --git a/content/relay-operations/community-resources/swag/contents.lr b/content/relay-operations/community-resources/swag/contents.lr
index b1c1419..53fa7bb 100644
--- a/content/relay-operations/community-resources/swag/contents.lr
+++ b/content/relay-operations/community-resources/swag/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: Swag
---
body:
@@ -7,12 +9,12 @@ body:
You can get one of these fine Tor T-shirts for contributing to the Tor project. There are two primary ways of contributing:
* Operate a fast Tor relay that's been running for the past two months: you are eligible if you allow exits to port 80 and you average 250 KBytes/s traffic, or if you're not an exit but you average 500 KBytes/s traffic.
-
+
* Help out in other ways. Maintain a translation. Run Tor trainings. Write a good support program and get a lot of people to use it. Do research on Tor and anonymity, solve some of our bugs, or establish yourself as a Tor advocate.
If you're operating a fast relay or you've done something else cool, email us at tshirt at torproject.org with the details. (We want to make sure our shirts help outreach happen all around the world, so please understand if we can't send you 5 shirts for your 5 excellent relays.)
-There are a variety of colors, shapes, and sizes available in the great roots design that Leiah Jansen made for us, as well as some older designs.
+There are a variety of colors, shapes, and sizes available in the great roots design that Leiah Jansen made for us, as well as some older designs.
---
html: two-columns-page.html
---
diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr
index 0e37f24..e3b67a3 100644
--- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr
+++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: Tor Abuse Templates
---
body:
diff --git a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr
index 7529051..8734580 100644
--- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr
+++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr
@@ -1,10 +1,12 @@
_model: page
---
+color: primary
+---
title: Tor Exit Guidelines
---
body:
-These guidelines are meant to give you a quick introduction into the business of running your own exit relay.
+These guidelines are meant to give you a quick introduction into the business of running your own exit relay.
NOTE:
This FAQ is for informational purposes only and does not constitute legal advice.
diff --git a/content/relay-operations/community-resources/tor-relay-universities/contents.lr b/content/relay-operations/community-resources/tor-relay-universities/contents.lr
index a3640bd..0b88a90 100644
--- a/content/relay-operations/community-resources/tor-relay-universities/contents.lr
+++ b/content/relay-operations/community-resources/tor-relay-universities/contents.lr
@@ -1,5 +1,7 @@
_model: page
---
+color: primary
+---
title: Tor Relay Universities
---
body:
@@ -82,7 +84,7 @@ Note that in many cases you don't even need to be researching the exit node itse
Subscribe to [Tor Relays Universities](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays-universities) mailing list (and other education institutions too).
---
-cta:
+cta:
---
html: two-columns-page.html
---
More information about the tor-commits
mailing list