Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #19034

Closed (moved)
Open
Opened 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 admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#19034