Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 971
    • Issues 971
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 24
    • Merge requests 24
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #18470
Closed
Open
Issue created Jul 08, 2021 by anonym@anonymMaintainer3 of 3 checklist items completed3/3 checklist items

TCA should stop Tor from trying to connect when we reach the error screen

This issue was inspired by: !435 (comment 173154)

Basically, now that TCA SAVECONF:s all the time, if we fall back to default bridges but fail, then we have a torrc which says we should use the default bridge, so if we restart TCA (e.g. after changing network to one where Tor is not blocked) it will immediately connect to the default bridge. This feels wrong.

So, perhaps TCA should try to reset the configuration after failures? I.e. drop all bridges, proxies and set DisableNetwork = 1 again and SAVECONF?

Tasks:

  • Adjust test suite (grep 18470 there)
  • Revert 3638ec1d
  • Remove the comment added by d7c30c17
Edited Aug 16, 2021 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking