#27167: track "first" OR_CONN -------------------------+------------------------------------------------- Reporter: | Owner: (none) catalyst | Type: task | Status: new Priority: Medium | Milestone: Tor: 0.3.5.x-final Component: Core | Version: Tor/Tor | Keywords: usability, ux, ux-team, bootstrap, Severity: Normal | 035-roadmap-subtask, 035-triaged-in-20180711, | s8-bootstrap Actual Points: | Parent ID: #27103 Points: | Reviewer: Sponsor: | -------------------------+------------------------------------------------- Right now the first stages of the "first" OR_CONN get reported as `BOOTSTRAP_STATUS_CONN_DIR` and `BOOTSTRAP_STATUS_HANDSHAKE` (the latter is a special bootstrap phase that gets translated into `BOOTSTRAP_STATUS_HANDSHAKE_DIR` or `BOOTSTRAP_STATUS_HANDSHAKE_OR` depending on how much progress was previously reported. The logic in functions that report these events should be moved up to a new abstraction so lower level code has to track less high-level state.
This also eliminates some logic in `control_event_bootstrap()` that tries to figure out whether a given handshake attempt corresponds to a directory connection or an application circuit connection. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27167> 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