Automatically use another guard when an onion service appears unreachable

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.

added component::applications/tor browser in Legacy / Trac owner::tbb-team in Legacy / Trac parent::27655 in Legacy / Trac priority::medium in Legacy / Trac resolution::wontfix in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac type::enhancement in Legacy / Trac labels

clarification not to change TB's guards, but to try others as well.

Trac:
Description: 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 configurable.

to

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.

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.

Trac:
Status: new to needs_information

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)?

Trac:
Cc: N/A to asc, dgoulet

closing this since it's totally off track

Trac:
Resolution: N/A to wontfix
Status: needs_information to closed

closed

moved from legacy/trac#27659 (moved)

added Feature label and removed 1 deleted label

removed 1 deleted label