<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hello Marcus,<br><br>Thank you very much for that explanation. Maybe it would be a good idea to make better mention of it on the TBB homepage ( http://check.torproject.org/ )?<br><br>All the best<br><br>--- On <b>Mon, 7/6/09, Marcus Griep <i><tormaster@xpdm.us></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Marcus Griep <tormaster@xpdm.us><br>Subject: Re: *3rd 'bad' IP*...Exit node IP *not* showing up on TorCheck and others<br>To: or-talk@freehaven.net<br>Date: Monday, July 6, 2009, 6:04 PM<br><br><div class="plainMail">On Mon, 2009-07-06 at 10:40 -0700, Chris Humphry wrote:<br>> Damit!<br>> <br>> It just happened again. This is starting to worry me a little bit.<br>> Am I really the only person who uses TBB and who is experince this<br>>
issue?<br>> <br>> I just started a new session of TBB and I have found a 3rd IP 'bad'<br>> address:<br>> <br>> IP: 67.166.145.75<br>> <br>> FQDN: c-67-166-145-75.hsd1.ca.comcast.net<br>> --- On Mon, 7/6/09, Chris Humphry <<a ymailto="mailto:humphry.chris@yahoo.com" href="/mc/compose?to=humphry.chris@yahoo.com">humphry.chris@yahoo.com</a>> wrote:<br>> Can someone *please* respond to my message this time? Can you tell me<br>> why this is happening? Or maybe just fix it? <br>> <br>> "I just started a session of TBB (current release) and when the<br>> homepage opened up it told me I was not connected to the Tor network.<br>> So I went to TorCheck and it told me the same thing. Then I used<br>> NewNym (via 'New Identity' in Vidalia) and with the new Exit node IP<br>> both TorCheck and the homepage for TBB now show I am connected to the<br>> network." <br>>
<br>> Last month the IP address I came across was: 76.73.58.224<br>> <br>> Just now I came across another IP address: 78.53.96.30 <br>> <br><br>What you are experiencing happens from time to time and is completely<br>normal. If the IP you are showing on the TorCheck page isn't your own,<br>then you're probably ok.<br><br>The reason that this happens is that there is a desync between when your<br>node learns about freshly started exits and when various tools update<br>their caches. Your node may pickup and use a new exit node that has not<br>yet been grabbed into the cache backing the TorCheck page. This also<br>applies for the TorStatus listing over at kgprog.<br><br>These generally work off cached copies of authority statuses, not<br>authorities themselves.<br><br>In this way, the TorCheck page is biased toward false positives than<br>false negatives, which is the preference. It would be much worse to let<br>someone who needs to use the
network to think they were anonymized when<br>they really weren't than it would be to tell someone who was properly<br>anonymized that they may not be using the network.<br><br>Also, I just checked the IP address that you listed above. It is now<br>listed as an exit in the TorStatus page, but with an uptime of less than<br>a day. Hence, it fits well into this scenario.<br><br>You can always check to see if the node is listed in your<br>cached-descriptors:<br><br>~$ grep 67.166.145.75 /var/lib/tor/cached-descriptors<br>router AlladinSane 67.166.145.75 443 0 9030<br>reject 67.166.145.75:*<br><br>A quick heuristic looking at this notes that it rejects exits to itself.<br>As this is part of the default exit policy, you can reasonably assume<br>this node is set up to be an exit.<br><br>-- <br>Marcus Griep<br>GPG Key ID: 0x070E3F2D<br>——<br><a href="https://torproj.xpdm.us" target="_blank">https://torproj.xpdm.us</a><br>Ακακια את.ψο´,
3°<br></div></blockquote></td></tr></table><br>