-
Notifications
You must be signed in to change notification settings - Fork 73
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
Make it possible to debug if a configured hidden service is working and eventually reinitialize it #327
Comments
@meejah: do you have by the chance any ready recipe for this that could be applied on txtorcon 0.19.3? |
Hmm.. (I have seen onions occasionally use connectivity .. but I'm not very clear on the details of how/when services change introduction-points or any differences between torrc and ADD_ONION services. Have you asked in |
I guess another solution would be to just try to connect to the service periodically. Perhaps this can even happen from the same GlobalLeaks client? (No idea about the privacy implications of that though..) |
GlobaLeaks opens a single connection and keeps it open. The syntom is that after a while even if the connections is kept open and do not fail, the hidden service become unreachable by users trying to reach it via the TorBrowser |
The reason I suggest asking Of course, if there's something txtorcon can do to help with this, I'm definitely game to add some code! :) For example, maybe a built-in monitor or so that periodically tries to build (additional) circuits to the Introduction Points? Again, though, this is worth some |
p.s. to clarify: these are v2 services only, right? Or does GlobalLeaks use v3 now? |
@evilaliv3 what version of Tor are you using? |
@meejah v2 on 0.3.3.9 |
Many of the @globaleaks users have encountered situations in which hidden servers instantiated via TxTorcon seems to lose reachability.
It would be really interesting if it could be made possible to debug if a configured hidden service is working and eventually reinitialize it.
The text was updated successfully, but these errors were encountered: