On Sun, Mar 04, 2007 at 07:24:10AM -0800, Anon Mus wrote: [Reformatted: lines wrapped. You might want to see if you can get your mailer to wrap lines to 72 characters.] > (v0.1.1.26 client on Win2Ksp4+) > > I have a few nodes I exclude in my torrc with ExcludeNodesconfiguration. > > When I start tor (using vidalia) I get a series of error messages in > mylog. eg > > [Warning] router_get_by_nickname(): You specified a server "xxx" > byname, but the directory authorities do not have a listing for > thisname. To make sure you get the same server in the future, refer > to itby key, as "$xxxxx". > > Yet these servers are all in my tor directory file and on > xenobite'slisting https://torstat.xenobite.eu/. It is possible for the servers to appear in your directory without having a listing _by name_. Servers are listed as "Named" by directory authorities if the nickname has been registered with the directory authorities, and no other server is allowed to canonically use it. If the name isn't registered, then any server can claim to have that name. This is why Tor is suggesting that you identify servers by key, not name. I'll change this warning so it is more clear; thanks for the tip. > I've noticed I even get routes (1st hop) to some of them, perhaps > thisis because router_get_by_nickname() fails. > > I believe keys can change, so I use nicknames because they always > seemto be there. Identity keys don't change for a given server, unless the server admin deletes the old identity key and generates a new one. > Also how do I turn off logging of > > [Warning] fetch_from_buf_socks(): Your application (using socks5 > onport 80) is giving Tor only an IP address. Applications that do > DNSresolves themselves may leak information. Consider using Socks4A > (e.g.via privoxy or socat) instead. For more information, please > seehttp://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS. > > without turning off all the warning logging. I don't think there is an easy way to turn off just this warning right now; we're going to re-do how DNS happens in the next development series (after 0.1.2.x), and stuff might improve then. There _is_ a workaround that might help, but it's ugly. Tor doesn't warn about mapped addresses, so you could try this: if your application's "localip/url cache" currently has a mappings like this: tor.eff.org -> 209.237.230.67 archives.seul.org -> 18.244.0.188 Then instead have your application's cache map to internal addresses tor.eff.org -> 10.10.0.1 archives.seul.org -> 10.10.0.2 And have Tor map those addresses to the ones you really want, by adding to the torrc: MapAddress 10.10.0.1 tor.eff.org MapAddress 10.10.0.2 archives.seul.org ## Or use IPs directly: #MapAddress 10.10.0.1 209.237.230.67 #MapAddress 10.10.0.2 18.244.0.188 This approach has two advantages besides suppressing warnings: - It only suppresses warnings for the addresses where you have a local mapping, so you still find out if you missed an address. - By giving your application 10.x addresses instead of actual addresses, you ensure that your application won't connect if it somehow forgets to use socks5. > I use plenty of socks > 5linked apps which will have the ip resolved. I also have a > localip/url cache which will also resolve them. I understand why its > thereI'd just like to turn them off. They get in the way. hope this helps, -- Nick Mathewson
Attachment:
pgpav9KHOx5vH.pgp
Description: PGP signature