[tor-bugs] #18142 [Tor]: Anti-Automated-Scanning: Support "marking" with iptables TCP connections differently "for each circuits"

[Tor Bug Tracker & Wiki]

#18142: Anti-Automated-Scanning: Support "marking" with iptables TCP connections
differently "for each circuits"
-------------------------+----------------------------------
 Reporter:  naif         |          Owner:
     Type:  enhancement  |         Status:  new
 Priority:  Low          |      Milestone:  Tor: unspecified
Component:  Tor          |        Version:  Tor: unspecified
 Severity:  Normal       |     Resolution:
 Keywords:  tor-core     |  Actual Points:
Parent ID:               |         Points:
  Sponsor:               |
-------------------------+----------------------------------

Comment (by naif):

 Well, we are not speaking about encryption, that can be secure or
 unsecure, 0 or 1, but about implementing features that could enable to
 slowdown most automated scanning (but not fix with 100% result automated
 scanning, that's just impossibile).

 Given the assumption that most automated scanners works with normal
 software, that's does not employ Tor specific optimizations other than
 supporting Socks, this measure could be effective, where effective means
 "reducing the amount of automated scanning" .

 It's like for the chinese GFW, it's an arm race and there's no definitive
 lethal weapon that's going to make us win the war, but we can still fight.

 Said that i think that's really something worth experimenting to reduce
 the impact of automated scan on Tor Relay operators, enabling ppl like me
 with sysadmin, network and security skills to experiment the approach.

 Fabio
 p.s. I also opened up a new idea to reduce the impact of automated
 scanning, but it's really more complicated
 https://lists.torproject.org/pipermail/tor-talk/2016-January/040011.html

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18142#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online