Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 832
    • Issues 832
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • 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
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #19034

Closed
Open
Created May 11, 2016 by teor@teor

Declaring authorities with matching relay keys should fail

If a:

  • hard-coded entry or
  • config entry, tries to add:
  • an authority,
  • a bridge authority, or
  • a fallback directory, with the same:
  • relay key,
  • v3ident key,
  • IPv4 address and ORPort (matching any other IPv4 address and port), or
  • IPv4 address and DirPort (matching any other IPv4 address and port),
  • IPv6 address and ORPort (matching any other IPv6 address and port), or
  • IPv6 address and (IPv4) DirPort (matching any other IPv6 address and port), as an existing entry, tor should warn and refuse to start.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking