torproject / tor Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug #27049: Consider hs circs before deciding no circuits are open. #263
base: maint-0.3.3
Are you sure you want to change the base?
Conversation
…open. Fix changes file bug number typos.
Pull Request Test Coverage Report for Build 3183
|
src/or/circuitlist.c
Outdated
| @@ -625,7 +625,7 @@ circuit_any_opened_circuits(void) | |||
| TO_CIRCUIT(next_circ)->state == CIRCUIT_STATE_OPEN && | |||
| TO_CIRCUIT(next_circ)->purpose != CIRCUIT_PURPOSE_C_MEASURE_TIMEOUT && | |||
| next_circ->build_state && | |||
| next_circ->build_state->desired_path_len == DEFAULT_ROUTE_LEN) { | |||
| next_circ->build_state->desired_path_len >= DEFAULT_ROUTE_LEN) { | |||
How does that work with single onion service circuits? I'm not entirely sure, because of preemptive circuit building, if a tor client can NOT have at least 3-hop circuits but I'm guessing their could be a window that it can happen?
Hrmm yeah. Ok. We should count SoS circuits here, too. Tried to do that in this commit: 8c950e7
changes/bug27409
Outdated
| @@ -0,0 +1,6 @@ | |||
| o Minor bugfixes (onion services): | |||
| - When circuits timeout, count other other onion service circuits when | |||
…open. Handle single hop onion services.
…open. Fix changes typo.
| if (!circ->build_state) | ||
| return 0; | ||
|
|
||
| if ((circ->rend_data || circ->hs_ident) && |
Does this test cover single-hop into and rend circuits?
(HSDir circuits are always 3 hops or more for single onion services.)
Every HS circuits have the identifier attached to them. I think this is enough to cover the intro/rend circuits because of the path length of 1.
The HSDir circuit with 3 hops will be caught by the next condition below it seems.
No description provided.
The text was updated successfully, but these errors were encountered: