#19969: tor client does not immediately open new circuits after standby -------------------------------------------------+------------------------- Reporter: weasel | Owner: Type: defect | Status: | needs_review Priority: High | Milestone: Tor: | 0.2.9.x-final Component: Core Tor/Tor | Version: Tor: | 0.2.8.6 Severity: Normal | Resolution: Keywords: regression 029-backport | Actual Points: 028-backport | Parent ID: | Points: 2 Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by arma): I'm running bug19969_028_small and it seems to work under normal operation. {{{ Oct 31 22:50:11.329 [debug] connection_ap_handshake_attach_circuit(): Attaching apconn to circ 2444682090 (stream 0 sec old). Oct 31 22:50:12.329 [debug] connection_ap_handshake_attach_circuit(): Attaching apconn to circ 2444682090 (stream 0 sec old). Oct 31 22:50:38.328 [debug] connection_ap_handshake_attach_circuit(): Attaching apconn to circ 2444682090 (stream 0 sec old). Oct 31 22:50:39.329 [debug] connection_ap_handshake_attach_circuit(): Attaching apconn to circ 2444682090 (stream 0 sec old). Oct 31 22:51:05.329 [debug] connection_ap_handshake_attach_circuit(): Attaching apconn to circ 2444682090 (stream 0 sec old). Oct 31 22:51:06.328 [debug] connection_ap_handshake_attach_circuit(): Attaching apconn to circ 2444682090 (stream 0 sec old). Oct 31 22:51:32.329 [debug] connection_ap_handshake_attach_circuit(): Attaching apconn to circ 2444682090 (stream 0 sec old). Oct 31 22:51:33.329 [debug] connection_ap_handshake_attach_circuit(): Attaching apconn to circ 2444682090 (stream 0 sec old). }}} I wonder if there are any good linking / cookie attacks if I become known as "the guy whose run_scheduled events is offset by 328 milliseconds?" :) And then running it on a bridge that I can't bootstrap from... I get a growing barrage of these "Optimistically trying directory fetches again" lines, one for every open socks request, every time I get a new socks request. Yucko. In retrospect when we did the 'retry' parameter, we should have put a flag on each entry_connection_t, and then just tried to attach the ones that had the flag set. Easy to say in retrospect. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19969#comment:30> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs