[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #5028 [Ooni]: Tor bridge scanning



#5028: Tor bridge scanning
---------------------+------------------------------------------------------
 Reporter:  hellais  |          Owner:  runa                     
     Type:  project  |         Status:  assigned                 
 Priority:  normal   |      Milestone:  Sponsor F: March 15, 2012
Component:  Ooni     |        Version:                           
 Keywords:           |         Parent:                           
   Points:           |   Actualpoints:                           
---------------------+------------------------------------------------------
Changes (by runa):

 * cc: aagbsn (added)


Comment:

 Replying to [comment:14 arma]:
 > Doing a full Tor connection to a bridge from inside China is a poor
 idea. Doing a TCP scan to the bridge address is probably fine, and I think
 it would tell us everything we need to know at this point.

 Ok, we'll do that.

 > If we wanted to be extra cautious we could do the scan on all the
 bridges in the https bucket, since they're more likely to be known
 already. I think we don't have a script to pull out just those bridges
 from the bridgedb database; but that's 'a simple matter of programming' as
 they say.

 Who can do this? Aaron? Would be great if Arturo, Karsten, and I could
 have an email with the bridge addresses in it.

 > But yes, Karsten's point about "automated" is an important one: we
 should script a periodic export of a list of bridges to scan, cron a
 periodic scan, and add each set of scan results to some long-term storage
 in a way that is easy to do analysis on.

 Yes, we should, but that's something we can focus on after March 15th.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5028#comment:15>
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