Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,004
    • Issues 1,004
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor Browser
  • Issues
  • #40496
Closed
Open
Created Jun 29, 2021 by Matthew Finkel@sysrqbMaintainer

OnionRewrite fails after upgrade

In a fresh instance, the new ruleset from #40456 (closed) is successfully installed and it works. However, when upgrading from a previous version somethings goes wrong, and while the #40456 (closed) "works" (the old ruleset is deleted and the new one is added), the ruleset is apparently not applied. The symptom is that https-everywhere does not redirect the request from *.securedrop.tor.onion -> *.onion and Tor Browser simply sends the *.securedrop.tor.onion hostname to tor. As a result, tor responds with a BAD_HOSTNAME because securedrop.tor.onion is a bad hostname.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking