diff options
| author | Roger Dingledine <arma@torproject.org> | 2016-04-12 19:54:04 -0400 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2016-04-12 19:54:04 -0400 |
| commit | 0aacc070369d7f9614de9132b2f9e567b96a20bf (patch) | |
| tree | b655cd03ac4d2e0e881267927cfd56be6e9afb3a /src | |
| parent | bd34edc18d6e21f5ba7bddf5a7ebe6582e8dc639 (diff) | |
| download | tor-0aacc070369d7f9614de9132b2f9e567b96a20bf.tar.gz tor-0aacc070369d7f9614de9132b2f9e567b96a20bf.zip | |
encourage rejected relays to contact us
When the directory authorities refuse a bad relay's descriptor,
encourage the relay operator to contact us. Many relay operators
won't notice this line in their logs, but it's a win if even a
few learn why we don't like what their relay was doing.
Resolves ticket 18760.
I didn't specify a contact mechanism (e.g. an email address), because
every time we've done that in the past, a few years later we noticed
that the code was pointing people to an obsolete contact address.
Diffstat (limited to 'src')
| -rw-r--r-- | src/or/dirserv.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/or/dirserv.c b/src/or/dirserv.c index f012b7bf64..f27fb28965 100644 --- a/src/or/dirserv.c +++ b/src/or/dirserv.c @@ -349,7 +349,7 @@ dirserv_get_status_impl(const char *id_digest, const char *nickname, if (result & FP_REJECT) { if (msg) - *msg = "Fingerprint is marked rejected"; + *msg = "Fingerprint is marked rejected -- please contact us?"; return FP_REJECT; } else if (result & FP_INVALID) { if (msg) @@ -367,7 +367,7 @@ dirserv_get_status_impl(const char *id_digest, const char *nickname, log_fn(severity, LD_DIRSERV, "Rejecting '%s' because of address '%s'", nickname, fmt_addr32(addr)); if (msg) - *msg = "Authdir is rejecting routers in this range."; + *msg = "Suspicious relay address range -- please contact us?"; return FP_REJECT; } if (!authdir_policy_valid_address(addr, or_port)) { |