[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1930 [Tor Client]: Hidden service fails after getting new v2 descriptor
#1930: Hidden service fails after getting new v2 descriptor
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: minor | Milestone: Tor: post 0.2.2.x
Component: Tor Client | Version: Tor: 0.2.2.15-alpha
Keywords: | Parent:
------------------------+---------------------------------------------------
Comment(by arma):
Are the old intro and rend circuits still sitting around, and they haven't
been marked as worth giving up on? Maybe we should mark old circuits with
this hidden service fingerprint on them as part of
rend_client_desc_trynow().
Presumably I had a version of the v2 rendezvous descriptor sitting around
from the last time I accessed this hidden service, which looks like it was
over 48 hours ago:
{{{
Sep 08 01:22:34.389 [info] connection_dir_client_reached_eof(): Received
rendezvous descriptor (size 3258, status 200 ("OK"))
Sep 08 01:22:34.390 [debug] rend_cache_store_v2_desc_as_client():
Successfully stored rend desc 'sw4...', len 3258.
Sep 08 01:22:34.390 [info] connection_dir_client_reached_eof():
Successfully fetched v2 rendezvous descriptor.
}}}
That doesn't sound like a "Descriptor is here. Great." situation.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1930#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs