v3 client confused about which servers are named
Running r11968 as a client, it complains about things like Oct 16 01:05:36.303 [warn] You specified a server "DrazziBTorNode" by name, but this name is not registered, so it could be used by any server, not just the one you meant. To make sure you get the same server in the future, refer to it by k ey, as "$F268430A96705AC0BB52117AC5122F4DC934727E".
It turns out this is caused by vidalia doing a getinfo on this nickname. I caught Tor while Vidalia was asking about Bellum: #0 router_get_by_nickname (nickname=0x8306672 "Bellum", warn_if_unnamed=1) at routerlist.c:1783 #1 0x08083c5e in getinfo_helper_dir (control_conn=0x8681e20, question=0x8306668 "desc/name/Bellum", answer=0xbfc4342c) at control.c:1314 legacy/trac#2 (closed) 0x08085d1b in handle_getinfo_helper (control_conn=0x8681e20, question=0x8306668 "desc/name/Bellum", answer=0xbfc4342c) at control.c:1804 legacy/trac#3 (closed) 0x08085df0 in handle_control_getinfo (conn=0x8681e20, len=19, body=0x8adda00 "desc/name/Bellum\r\n") at control.c:1829 legacy/trac#4 (closed) 0x08088670 in connection_control_process_inbuf (conn=0x8681e20) at control.c:2685 legacy/trac#5 (closed) 0x0807442e in connection_process_inbuf (conn=0x8681e20, package_partial=1) at connection.c:2638 legacy/trac#6 (closed) 0x080725a1 in connection_handle_read (conn=0x8681e20) at connection.c:1813 legacy/trac#7 (closed) 0x080adfc0 in conn_read_callback (fd=24, event=2, _conn=0x8681e20) at main.c:470 legacy/trac#8 (closed) 0xb7ee6c79 in event_base_priority_init () from /usr/lib/libevent-1.1a.so.1 legacy/trac#9 (closed) 0xb7ee6f65 in event_base_loop () from /usr/lib/libevent-1.1a.so.1 legacy/trac#10 (closed) 0xb7ee6dcb in event_loop () from /usr/lib/libevent-1.1a.so.1 legacy/trac#11 (closed) 0x080afe3b in do_main_loop () at main.c:1389 legacy/trac#12 (closed) 0x080b127d in tor_main (argc=1, argv=0xbfc43804) at main.c:1928 legacy/trac#13 (closed) 0x080e90e2 in main (argc=Cannot access memory at address 0x0 ) at tor_main.c:28
It turns out there was a circuit building at that time: Oct 16 01:26:41.539 [info] exit (high-uptime) circ (length 3, exit chaoscomputer club23): $5C854C6CE50727F32E51274B1CF4DF9693A206EA(open) Bellum(open) $4121B07A3 86AA1A8015D618D213B1980BA388487(closed)
Now, clearly some part of Tor thought Bellum was Named, so it used the nickname. But then the other part of Tor thought it wasn't.
In this case, the cached-consensus file said r Bellum 7j/MKmnxheiRBy8T7pkIzW7ZvqU 22tvSKhAXrqKWmvs53JdUlWDr70 2007-10-15 22:2 7:52 184.108.40.206 9001 9030 s Fast Guard Named Running Stable V2Dir Valid v Tor 0.1.2.14
but in my cached-status/* directories, which haven't been updated in a few hours since I'm allegedly not using them anymore, tor26's networkstatus didn't have an entry for Bellum -- so according to v2 it wouldn't be considered Named.
[Automatically added by flyspray2trac: Operating System: All]