Skip to content
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

Wake up Tor on "552 no descriptor for X" #251

Open
meejah opened this issue Sep 12, 2017 · 0 comments
Open

Wake up Tor on "552 no descriptor for X" #251

meejah opened this issue Sep 12, 2017 · 0 comments

Comments

@meejah
Copy link
Owner

meejah commented Sep 12, 2017

If Tor is dormant and txtorcon connects and tries to build a circuit, this may fail with 552 no descriptor for X because Tor still fetches enough consensus to know about new/current relays, but doesn't fetch (micro)descriptors if it is dormant.

GETINFO dormant will tell us if Tor is dormant. So: if there's a .build call in progress, and we get a 552, and Tor is dormant, we should wake it up. Recommended way to do this is to resolve a DNS or try to connect to soemthing (e.g. we could do a lookup for torproject.org via SOCKS).

Thanks to arma and teor on #tor-dev for discussion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant