[tor-bugs] #24526 [Core Tor/Tor]: Make it clear that multi-relay operators are expected to set a working ContactInfo and proper MyFamily
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Dec 14 00:13:38 UTC 2017
#24526: Make it clear that multi-relay operators are expected to set a working
ContactInfo and proper MyFamily
--------------------------+------------------------------------
Reporter: cypherpunks | Owner: (none)
Type: enhancement | Status: new
Priority: Medium | Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-doc, man | Actual Points:
Parent ID: #24497 | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------------
Comment (by cypherpunks):
Part 1: Make ContactInfo mandatory for operators running multiple relays /
bridges:
based on the email from David (4 Dec 2017 18:07:08 -0500) on bad-relays
I'm submitting a patch to make it clear to relay/bridge operators that a
contact information is mandatory if you run more than one relay.
This should make bad-relays@ cases less problematic where we have a
presumed relay group like [ 1 ] and have no way to contact the operator
before removing these relays from the tor network (because historically
such groups turned out to be malicious).
I didn't add to the man page what happens if you do not set it (your
relays might get removed if we detect a very likely group of relays
without contactInfo [ 1 ]), because that would make it longer.
This adds a single and clear statement to the ContactInfo entry.
tor.1.txt:
{{{
@@ -1716,7 +1716,8 @@
[[ContactInfo]] **ContactInfo** __email_address__::
Administrative contact information for this relay or bridge. This
line
can be used to contact you if your relay or bridge is misconfigured
or
- something else goes wrong. Note that we archive and publish all
+ something else goes wrong. ContactInfo must be set if you run more
than
+ one relay or bridge. Note that we archive and publish all
descriptors containing these lines and that Google indexes them, so
spammers might also collect them. You may want to obscure the fact
that it's an email address and/or generate a new address for this
}}}
[ 1 ] https://nusenu.github.io/OrNetRadar/2017/11/30/a6
As David suggested after the man page is updated (this should get
backported), David plans to announce this change on the blog.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24526#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list