<div>Once the next phase is complete, I'll import all the data onto graphs so we can see where problems are occuring. Is there a centralized database of what tor nodes correspond to what countries? It would be interesting to see what countries are the fastest, or where weird errors are concentrated. There's a chance that some governments may be subtly making tor hard to use or that some network routers have problems with certain sequences of connections or something.
</div>
<div>Ringo<br><br> </div>
<div><span class="gmail_quote">On 12/17/06, <b class="gmail_sendername">Mike Perry</b> <<a href="mailto:mikepery@fscked.org">mikepery@fscked.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Thus spake Ringo Kamens (<a href="mailto:2600denver@gmail.com">2600denver@gmail.com</a>):<br><br>> Thanks for that. It's interesting to have that data visualized.
<br><br>Yeah, it's not quite as immediately relevant as exit scanning, but it<br>is a little more interesting with respect to studying the network as a<br>whole I think. What I'm really looking forward to is gathering some
<br>statistics on most common peers during failure. I'm curious if those<br>OR_CONN_CLOSED are happening because certain nodes are<br>unreachable or partitioned from one another somehow, or if it is<br>something else. But I need better structure & object support for that
<br>than perl can provide sanely, unfortunately.<br><br>I've gone back to scanning exits in the meantime. If anyone wants to<br>join me with a different wordlist.txt, set of filetypes and other ssh<br>hosts, it might be nice.
<br><br>--<br>Mike Perry<br>Mad Computer Scientist<br><a href="http://fscked.org">fscked.org</a> evil labs<br></blockquote></div><br>