[tor-dev] Design for an exit relay scanner: feedback appreciated

Lunar lunar at torproject.org
Tue Nov 26 14:21:04 UTC 2013

Philipp Winter:
> I now have similar code which is based on stem:
> https://github.com/NullHypothesis/exitmap
> However, the problem with a parallel single-Tor-process design
> is that there is no easy way for scanning modules to figure out
> which exit relay they were attached to.  The Tor controller just
> sees a bunch of incoming streams but once, one of these streams
> spots something fishy, it is difficult to figure out which exit
> relay is to blame.

I am unsure about the meaning of the `cmd` parameter in the probe method
of your modules. But, can't you pass the circuit ID (or an opaque
wrapper object, actually) to the scanning module, and have the scanning
module pass that to the stream attacher when it has a stream ready?

(Feel free to ignore me if that sounds like non-sense. I only had a
quick look at the code.)

Lunar                                             <lunar at torproject.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20131126/ffd9e0be/attachment.sig>

More information about the tor-dev mailing list