<div dir="ltr"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">OK, understood. I thought you had specified the Python code you were<br>
using.. it appears to use multiple exits.<div class="Ih2E3d"></div></blockquote><div class="Ih2E3d"> <br>Yes, I have to make tests, if bug depends on multiple exits or just on number of circuits... But I think it should make somebody who knows Tor better than me, because I cannot find many consequences from high level point of view.<br>
<br>Are tor developers reading this conference?<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You need to try to identify the rogue exit node (or nodes) so we can<br>
exclude it from our circuit builds. It could be an overflow but it could</blockquote><div><br>I dont think it is problem of corrupted exit node. Btw, I tested many circuits because Im writing tor exit node scanner as school project ;). But of course, it was not intention to make TOO MUCH circuits.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Yes, but my point was it had to be admixture of the "clear" unencrypted<br>
streams rather than encrypted streams, otherwise you would get garbage<br>
out. Buffer overflow or not.<div class="Ih2E3d"></div></blockquote><div><br>I think unencrypted communication is the most frequent, so there is big probability that I can see unencrypted communication than something fuzzy. But it is only subjective tip.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"> </div>
I guess that many of my page requests (I'm on 4mb broadband with dual<br>
processor) should be getting this kinda error, but I do not. I just see<br>
it once in a while (maybe once every 200+ pages) and then I try to zap<br>
the exit node if it occurs repeatedly. This makes me wonder why you are<br>
getting it so often.<br>
</blockquote><div><br>Because many of your requests go thru only one or two circuit at the moment. I was made only one request (open page in browser), but there were hundreds of circuits. It is the difference between "normal browsing" and "buggy behaviour". <br>
</div></div><br>Marek<br></div>