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

Remove the unnecessary and confusing hidden service self test #26

Closed
Antaon opened this issue Mar 29, 2014 · 1 comment · Fixed by #141
Closed

Remove the unnecessary and confusing hidden service self test #26

Antaon opened this issue Mar 29, 2014 · 1 comment · Fixed by #141
Labels
Milestone

Comments

@Antaon
Copy link

Antaon commented Mar 29, 2014

Specs: Torsion v1.0.0-10-g2c52502 on Debian 7 (64bit) in VirtualBox:

Repro Steps:

  1. Open the Torsion binary and successfully connect to the Tor network.
  2. Click the "Preferences" button/icon.
  3. Click the "Tor" tab.
  4. Wait 3 minutes looking for a notice about "Closing stream for '[scrubbed].onion': hidden service is unavailable (try again later)."

Results:
The Torsion program is making onion connections when the user has no contacts. This is worrying.

Expected Result: The Torsion program only make authorized onion connection attempts.

Notes:
Perhaps these unexplained and failing onion attempts are expected behavior as Torison could be using a Hidden service for updates or for some other reason, but I don't recall any comment in the design or protocol documents mentioning it. Could it be attempting to connect to my own published ID (similar to how Torchat does it by default)?

@special
Copy link
Member

special commented Mar 29, 2014

You're right, that does seem suspicious ;)

At startup or when there's reason to believe that Tor was offline and is now back online, it attempts to connect to its own service as a self-test (source). That had valid intentions, but it's actually fairly useless right now: the only visible effect is that the word "Connected" changes to "Online", and a similar change in the Tor preferences page.

There aren't many cases where tor will believe it's able to establish circuits, but publishing a hidden service fails. The ones that do exist would be better addressed by getting more feedback out of tor. This had value before the circuit-established state was monitored, but I don't think it does anymore.

@special special added this to the 1.0.x milestone Apr 17, 2014
@special special added core and removed core labels Jul 28, 2014
@special special changed the title There are Unknown Onion Connections with Default Setup and no Contacts Remove the unnecessary and confusing hidden service self test Mar 17, 2015
special added a commit to special/ricochet that referenced this issue Mar 17, 2015
It's not necessary to self-test connectivity of the hidden service
immediately after we publish it. This information isn't used for
anything valuable, and in every observed situation, we already have a
good idea of whether our service is connectable or not based on tor's
circuit status.

It has also raised some concerns, because a new Ricochet client with no
contacts will start trying to connect to some scrubbed service in the
logs.

Fixes ricochet-im#26
wfr pushed a commit to wfr/ricochet-irc that referenced this issue Jul 27, 2021
libtego_ui, libtego: reimplemented global unread counter for macOS dock icon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants