[tor-relays] G-Core Labs and their humanoid robots
Tor Relays
torrelaysaregreat at gmail.com
Thu Jun 10 20:50:34 UTC 2021
> On Tue, Jun 08, 2021 at 01:56:33PM +0200, Tor Relays wrote:
> > Support agent 1:
> > It was blocked because automatic monitoring system find your activity
> > suspicious.
> > Now, trust level of your traffic for IP has been increased however the
> > traffic is still automatically monitored. If the system of automatization
> > identifies your traffic as illegitimate or if we receive an infringement
> > report, we'll have to disable ports once again.
>
> Right, this is the key part of the explanation.
>
> Typically the way these blocklists work is that they run "honey services"
> somewhere secret on the internet, often on ports like 80 that are
> different from the ones they will apply the blocklist to. And if anybody
> connects to their secret honey IP address on port 80, they call them a
> likely spammer and refuse to allow emails/etc to their other services
> from that address.
>
> And Tor exits are particularly susceptible to getting put on these kind
> of blocklists, because all it takes is one person trying to connect to the
> honey address, and bam the exit relay's IP address gets on the blocklist.
>
> And the "cross-protocol" nature of the blocking, where they see you do
> one protocol and then block you from doing a different protocol, also
> does not match well with Tor's notion of exit policies.
>
> I guess that the scale of jerks on the internet is huge compared to what
> they imagine is the scale of non-jerks on Tor, and so they have little
> incentive to change the design of their honeypot systems. :(
>
> --Roger
>
This would explain it when the relay in question would be an exit relay,
but it is an ordinary relay.
Maybe it impacts your own trust level when you frequently connect to IPs
with a bad reputation (e.g. exits).
Or they analyzed too much traffic they don't understand so they mark it
"suspicious" and when the trust level falls under some threshold their
first line of defense is blocking the SMTP ports and check back later.
Or a silent hack and the server indeed sent emails.
IP address spoofing.
A bug in Tor that allows exiting when it shouldn't.
When they don't provide any information it's only speculation and as a
customer you can't do anything but watch and keep up the security level.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20210610/6b785e20/attachment-0001.htm>
More information about the tor-relays
mailing list