Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Chutney
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • Chutney
  • Issues
  • #33596
Closed
Open
Issue created Mar 12, 2020 by teor@teor

Fix or disable mixed+hs-v2 for Tor 0.3.5

In legacy/trac#33379 (moved), we made some changes that broke mixed+hs-v2 on Tor 0.3.5. Strangely, hs-v2-min works fine.

It looks like it is caused by some microdescriptor download bugs that we fixed in 0.4.0 or 0.4.1.

When we finish the rest of legacy/trac#33232 (moved), or fix legacy/trac#33428 (moved), we should either:

  • fix this issue
  • require tor or tor-stable to be 0.4.1 or later in mixed+hs-v2
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking