[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5459 [Torflow]: Exit scanner should scan for Guard <-> Exit reachability
#5459: Exit scanner should scan for Guard <-> Exit reachability
-----------------------+----------------------------------------------------
Reporter: mikeperry | Owner: aagbsn
Type: defect | Status: assigned
Priority: major | Milestone:
Component: Torflow | Version:
Keywords: | Parent: #5456
Points: | Actualpoints:
-----------------------+----------------------------------------------------
Comment(by mikeperry):
In case anyone else is interested in this ticket, here's a paste of my
reply to some questions about it on #tor-dev:
12:52 < mikeperry> meejah: There are examples of circuit creation in the
torflow.git repository
12:53 < mikeperry> meejah: specifically
https://gitweb.torproject.org/torflow.git/blob/HEAD:/CircuitAnalysis/BuildTimes/buildtimes.py
12:58 < mikeperry> meejah: the way the exit scanners work right now is
that the main scanner soat.py keeps scanning over the network and
generating .result files. These result files are then picked up by
snakeinspector.py which is run from a cron job
12:58 < mikeperry> and snakeinspector.py mails particularly bad results to
a mailinglist
12:58 < mikeperry> this code lives in
https://gitweb.torproject.org/torflow.git/tree/HEAD:/NetworkScanners/ExitAuthority
12:59 < mikeperry> you don't have to integrate with that code, but I would
recommend using the path support routines used by buildtimes.py
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5459#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs