Age | Commit message (Collapse) | Author |
|
|
|
Also, explain why it's relevant for bootstrapping.
This is a comments-only patch.
|
|
We set this flag if we've launched the connection in order to
satisfy an origin circuit, or when we decide the connection _would_
satisfy an origin circuit. These are the only or_connections we
want to consider for bootstrapping: other or_connections are opened
because of client EXTEND requests, and they may succeed or fail
because of the clients' confusion or misconfiguration.
Closes #25061.
|
|
This is an automated commit made with a python script.
After running the automated script, I had to hand-revert the cases where it
made the conversion functions call themselves.
Additionally, I had to edit a variable declaration in control_bootstrap.c so
that the result of a const cast could be put in a const field.
|
|
Closes ticket 32720.
|
|
|
|
Also, split the formatting code shared by control.c and
control_events.c into controller_fmt.c.
|
|
introduced in 85542ee5
next step is to fix it in torspec too
|
|
|
|
The message for the "ap_conn_proxy" bootstrap status tag was missing
some text. Fixes bug 28929. Bug not in any released Tor.
|
|
Redefine the set of bootstrap phases to allow display of finer-grained
progress in the early connection stages of connecting to a relay.
This includes adding intermediate phases for proxy and PT connections.
Also add a separate new phase to indicate obtaining enough directory
info to build circuits so we can report that independently of actually
initiating an ORCONN to build the first application circuit.
Previously, we would claim to be connecting to a relay when we had
merely finished obtaining directory info.
Part of ticket 27167.
|
|
Replace a few invocations of control_event_bootstrap() with calls from
the bootstrap tracker subsystem. This mostly leaves behavior
unchanged. The actual behavior changes come in the next commit.
Part of ticket 27167.
|
|
|
|
It also no longer distinguishes the case of internal-only paths, which
was often wrong anyway. Closes ticket 27402.
|
|
Part of ticket 27402.
|