Opened 4 years ago

Last modified 2 years ago

#19034 new defect

Declaring authorities with matching relay keys should fail

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Minor Keywords: easy torrc configuration but-why tor-client
Cc: Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description (last modified by teor)

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.

Child Tickets

Change History (5)

comment:1 Changed 4 years ago by teor

Description: modified (diff)

comment:2 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:3 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:4 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:5 Changed 2 years ago by nickm

Keywords: torrc configuration but-why tor-client added
Severity: NormalMinor
Note: See TracTickets for help on using tickets.