Exit policy not working

[cozybeardev]

Hi,

I’m receiving reports from my hoster of smtp email spam. They provided traffic proof which showed traffic to port 465. How is this possible. My policies already block this for this very reason. Does anyone see anything badly configured here?

https://metrics.torproject.org/rs.html#details/2F76402F04EE7AC80207A4B3B525B235673952AE

[cozybeardev]

I’ll just deploy some iptables for now in parrallel. Ports are being on bypassed on at least 3 nodes now. Don’t ask me how. Perhaps the policy does not do what I expect it to do.

[Vort]

I saw similar complaint some time ago:

Why does a tor exit relay create outbound connection to destinations rejected by its exitpolicy?

Really surprised to see tor create connections to destinations that are rejected by its exit policy. What other reasons are there for tor to create outbound TCP connections to port 443 if the destination IP is not allowed by the exit policy? The destination is not a tor relay.

[cozybeardev]

Mirrored my exit policy into iptables and has been deployed on all exits I run. We’ll see if that fixes anything. Not sure if Tor does creative routing like Docker does. Time will tell.

For those curious that want to replicate; various fixes and tweaks · cozybear-dev/ansible-tor@ebac9f3 · GitHub