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

Re: Silly question...



Yep, it eventually came up and built a circuit just fine.

Was just curious...

Thanks!

- ferg


-- David Vennik <davidvennik@xxxxxxxxxxxxxx> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

you expressed exactly what my first thought was in response - that the
client was merely persistently attempting to use an old directory cache.

coderman wrote:
> On 10/24/06, Fergie <fergdawg@xxxxxxxxxxx> wrote:
>> ...
>> Oct 24 23:15:19:698 [Notice] Tor v0.1.2.2-alpha. This is experimental
>> software. Do not rely on it for strong anonymity.
>> ...
>> Oct 24 23:15:20:167 [Notice] We now have enough directory information
>> to build circuits.
>> Oct 24 23:15:25:276 [Notice] No Tor server exists that allows exit to
>> [scrubbed]:80. Rejecting.
>> ... [lots of rejection] ...
>> Oct 24 23:17:19:354 [Notice] Our directory information is no longer
>> up-to-date enough to build circuits.
>> Oct 24 23:17:19:386 [Notice] I learned some more directory information,
>> but not enough to build a circuit.
>> ... [x2]
>> Oct 24 23:17:23:651 [Notice] We now have enough directory information
>> to build circuits.
>> Oct 24 23:17:46:479 [Notice] Tor has successfully opened a circuit.
>> Looks like client functionality is working.
> 
> this looks like:
> - Tor was started with an old directory
> - thought it could create circuits
> - attempts to connect out (your new firefox?) failed because directory
> info was actually stale
> - got updated directory
> - working fine now?
> 
> 
>> ...
>> Why was an exit being created to: [scrubbed]:80
>>
>> What's up with that? Just curious...
> 
> i assume it was your 2.0 firefox using torbutton.  is anything else
> configured to use Tor as a socks proxy?
> 
> best regards,
> 
> 
> also:
> if Tor did think an out of date directory (cached?) was suitable for
> building circuits, shouldn't it defer until it has obtained a current
> directory?
> 


- --
http://davidvennik.blogspot.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFPyecgF+g21XtpK4RA7Z4AJ0bDwoubPWuFJIKmsfTIl4J1tktuACgx969
PsDfEfNqkuhtEMY63WfFGY8=
=1uYT
-----END PGP SIGNATURE-----