Opened 8 years ago

Last modified 2 years ago

#2282 new enhancement

Publish router descriptors rejected by the authorities or omitted from the consensus

Reported by: rransom Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-dirauth debugging diagnostic easy
Cc: karsten Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Right now, if a relay is dropped from the consensus, or its descriptor is rejected outright by the directory authorities, we won't find out that it has happened unless someone notices that their relay isn't working and tells us, and we can't find out why it happened unless we read the directory authorities' log files.

The directory authorities should:

  • archive all descriptors that are published to them, even if they are rejected or not included in the consensus;
  • if a descriptor is rejected, record the reason in that archive; and
  • if a relay is omitted from the consensus, record the reason in the archive.

The directory authority operators should:

  • examine a sample of the descriptors that are not included in the consensus, for whatever reason;
  • if the descriptors in the sample do not contain particularly sensitive information, begin publishing these otherwise unpublished descriptors.

Having this information available would make it easier to find relays that were disabled by #2204 and inform their operators that they need to upgrade Tor, for example.

Child Tickets

Change History (11)

comment:1 in reply to:  description Changed 8 years ago by rransom

Replying to rransom:

  • if a relay is omitted from the consensus, record the reason in the archive.

Currently, descriptors for relays that are omitted from the consensus are archived, and are visible on the consensus health page, but the reason the relay was omitted from the consensus does not seem to be there.

comment:2 Changed 8 years ago by arma

I approve of this general idea (for what it's worth :)

comment:3 Changed 8 years ago by Sebastian

I believe this is already covered by the proposed document that authorities should publish about relays that they know about. See proposal 164.

comment:4 Changed 8 years ago by arma

Component: Tor RelayTor Directory Authority

comment:5 Changed 8 years ago by karsten

See also #2763 which was closed as a duplicate of this ticket and which contains some discussion about changing metrics-db to archive all descriptors.

comment:6 Changed 8 years ago by nickm

Milestone: Tor: 0.2.3.x-final
Priority: majornormal

I'm not sure it falls under 164; 164 is about saying how you would vote in advance; this is about saying more info than would appear in a vote.

One trivial version of this is to append every rejected descriptor to a file.

comment:7 Changed 7 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: unspecified

comment:8 Changed 7 years ago by nickm

Keywords: tor-auth added

comment:9 Changed 7 years ago by nickm

Component: Tor Directory AuthorityTor

comment:10 Changed 2 years ago by dgoulet

Keywords: tor-dirauth added; tor-auth removed

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

comment:11 Changed 2 years ago by nickm

Keywords: debugging diagnostic easy added
Severity: Normal
Note: See TracTickets for help on using tickets.