[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Windows-specific bug? cached-routers ignored on start-up
- To: or-talk@xxxxxxxxxxxxx
- Subject: Windows-specific bug? cached-routers ignored on start-up
- From: "John Kimble" <det.j.kimble@xxxxxxxxx>
- Date: Thu, 7 Dec 2006 22:02:55 +0800
- Delivered-to: firstname.lastname@example.org
- Delivered-to: email@example.com
- Delivered-to: firstname.lastname@example.org
- Delivery-date: Thu, 07 Dec 2006 09:03:49 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=VLpu4iL3EbQLudIA3GNF9IyU414CGXSwhii0Ga/bAb9JmAsFOzyBxXjSQbdGLogoCrPTmSDubtNGAELockDw2ggwNeu5hSpbPw8o6g0TKuh1SWdNXfciaQW1AC7HjIVrtHlORC//X2ZYSiRPdq97YfgtdpvM28uQ0itMM5IKx+8=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
It seems the current Tor+Privoxy+Vidalia bundle (0.1.2.4-alpha)
running on Windows XP does not load server descriptors from
cached-routers on start-up.
Steps to reproduce the problem:
- Have a relatively fresh copy of cached-routers and cached-status/*
stored in the Tor data directory, obtained from another machine that
has been successfully running Tor.
- For the purpose of this experiment, we set "FetchServerDescriptors
0" and "FetchHidServDescriptors 0" in torrc, so that Tor has to depend
solely on the local cache for server descriptors.
- Start Tor.
- Tor reports, "I learned some more directory information, but not
enough to build a circuit." and stops there (since
FetchServerDescriptors was set to 0).
- Stop Tor.
- Rename cached-routers to cached-routers.new
- Start Tor again.
- Tor reports, "We now have enough directory information to build
circuits." and immediately starts building circuits.
It looks like Tor ignores cached-routers but reads cached-routers.new
if present. This occurs only in Windows. In Linux (also running Tor
0.1.2.4-alpha), both cached-routers and cached-routers.new are loaded
This would be nice to fix but not terribly urgent, since we can work
around it for now by renaming cached-routers to cached-routers.new
before starting Tor.