Opened 2 months ago
Closed 2 months ago
#27659 closed enhancement (wontfix)
Automatically use another guard when an onion service appears unreachable
| Reported by: | traumschule | Owned by: | tbb-team |
|---|---|---|---|
| Priority: | Medium | Milestone: | |
| Component: | Applications/Tor Browser | Version: | |
| Severity: | Normal | Keywords: | |
| Cc: | asc, dgoulet | Actual Points: | |
| Parent ID: | #27655 | Points: | |
| Reviewer: | Sponsor: |
Description (last modified by )
When TB's guard has an outdated descriptors list a TB user is unable to access the service with TB for some time.
Might be handy to make the number of guards to try in a row configurable.
Child Tickets
Change History (4)
comment:1 Changed 2 months ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 2 months ago by
| Status: | new → needs_information |
|---|
If this is related to establishing a connection with an onion service, then changing the guard should not solve the problem (in general). Using more guards is also something tor tries very hard not to do, so anything like this requires more discussion.
comment:3 Changed 2 months ago by
| Cc: | asc dgoulet added |
|---|
for an onion service, the descriptor is fetched from a hsdir, which is (roughly) a stable, relay in the tor network that (hopefully) isn't your guard
Is there anything we can do when hsdirs are missing descriptors (from a user / TB perspective)?
comment:4 Changed 2 months ago by
| Resolution: | → wontfix |
|---|---|
| Status: | needs_information → closed |
closing this since it's totally off track
clarification not to change TB's guards, but to try others as well.