Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • briar briar
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 788
    • Issues 788
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • briarbriar
  • Issues
  • #290

Closed
Open
Created Apr 12, 2016 by akwizgran@akwizgranOwner

Reset Tor polling state if guard connection is lost

If the Tor plugin loses its guard connection for reasons other than a change in the device's network connectivity (which we already detect), the plugin should reset its polling state, just as it would in response to a network connectivity change. Otherwise we could end up in the following situation:

  • Hidden service descriptor published
  • Stop polling
  • Guard connection lost, hidden service unreachable
  • Contact's hidden service descriptor published
  • Contact stops polling
  • Guard connection re-established
  • Hidden service descriptor republished
  • We never connect to the contact, they never connect to us

We already receive and log OR connection status events - the plugin should be able to use these to detect when our last OR connection closes and call the existing code for handling network connectivity changes.

Edited Nov 16, 2020 by akwizgran
Assignee
Assign to
Time tracking