Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2156

Closed (moved)
(moved)
Open
Created Nov 04, 2010 by Sebastian Hahn@sebastian

Time to abandon Tor 0.1.2.x?

I just tested an old 0.1.2.19 Tor, and it doesn't work as a client anymore (it can't bootstrap due to not having enough trusted directories available). We also have just three relays on 0.1.2.19 left, none of which are very big. If we finally manage to declare 0.1.2.x dead, we can drop a lot of old compatibility code from Tor in an 0.2.3.x timeframe. Are there reasons why we should not do this?

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