diff options
Diffstat (limited to 'control-spec.txt')
-rw-r--r-- | control-spec.txt | 26 |
1 files changed, 25 insertions, 1 deletions
diff --git a/control-spec.txt b/control-spec.txt index ef59bd3..77cc01c 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -1979,6 +1979,19 @@ [DROPOWNERSHIP was added in Tor 0.4.0.0-alpha] +3.34. DROPTIMEOUTS + + The syntax is: + "DROPTIMEOUTS" CRLF + + Tells the server to drop all circuit build times. Do not invoke this command + lightly; it can increase vulnerability to tracking attacks over time. + + Tor replies with "250 OK" on success. Tor also emits the BUILDTIMEOUT_SET + RESET event right after this "250 OK". + + [DROPTIMEOUTS was added in Tor 0.4.4.0-alpha.] + 4. Replies Reply codes follow the same 3-character format as used by SMTP, with the @@ -2144,7 +2157,9 @@ Purpose = "GENERAL" / "HS_CLIENT_INTRO" / "HS_CLIENT_REND" / "HS_SERVICE_INTRO" / "HS_SERVICE_REND" / "TESTING" / - "CONTROLLER" / "MEASURE_TIMEOUT" + "CONTROLLER" / "MEASURE_TIMEOUT" / + "HS_VANGUARDS" / "PATH_BIAS_TESTING" / + "CIRCUIT_PADDING" HSState = "HSCI_CONNECTING" / "HSCI_INTRO_SENT" / "HSCI_DONE" / "HSCR_CONNECTING" / "HSCR_ESTABLISHED_IDLE" / @@ -2193,6 +2208,12 @@ TESTING (reachability-testing circuit; carries no traffic) CONTROLLER (circuit built by a controller) MEASURE_TIMEOUT (circuit being kept around to see how long it takes) + HS_VANGUARDS (circuit created ahead of time when using + HS vanguards, and later repurposed as needed) + PATH_BIAS_TESTING (circuit used to probe whether our circuits are + being deliberately closed by an attacker) + CIRCUIT_PADDING (circuit that is being held open to disguise its + true close time) The "HS_STATE" field is provided only for hidden-service circuits, and only in versions 0.2.3.11-alpha and later. Clients MUST accept @@ -2243,6 +2264,9 @@ MEASUREMENT_EXPIRED (As "TIMEOUT", except that we had left the circuit open for measurement purposes to see how long it would take to finish.) + IP_NOW_REDUNDANT (Closing a circuit to an introduction point that + has become redundant, since some other circuit + opened in parallel with it has succeeded.) The "REMOTE_REASON" field is provided only when we receive a DESTROY or TRUNCATE cell, and only if extended events are enabled. It contains the |