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
  • #28812

Closed (moved)
(moved)
Open
Created Dec 10, 2018 by Trac@tracbot

Duplicates of nodes descriptors can be found in consensus files

Sometimes file cached-microdesc-consensus contains duplicates of some Tor nodes which differ only by keys. For example, today (Mon Dec 10 17:17:29 UTC 2018) I saw these duplicates:

r Petibonum KDU6jCRTrb2O4BRxMMRdnGegVNc 2018-12-10 15:21:54 92.137.2.39 443 8080
m pEBO+WeONS3MuvMCPHWM1QOJiMGVWjTucOdGHMmBRNc
s Running V2Dir Valid
v Tor 0.2.9.16
pr Cons=1-2 Desc=1-2 DirCache=1 HSDir=1 HSIntro=3 HSRend=1-2 Link=1-4 LinkAuth=1 Microdesc=1-2 Relay=1-2
w Bandwidth=0 Unmeasured=1

r Petibonum bwz/Y5pp8y6UH51RU28xDghyqrc 2018-12-10 15:44:54 92.137.2.39 443 8080
m +Zq4u8cRhLR4ry1bEPidvOtULBP/PCAsioLRZnRa1gQ
s Running V2Dir Valid
v Tor 0.2.9.16
pr Cons=1-2 Desc=1-2 DirCache=1 HSDir=1 HSIntro=3 HSRend=1-2 Link=1-4 LinkAuth=1 Microdesc=1-2 Relay=1-2
w Bandwidth=95

Is it a bug? Now [node] is out of consensus.

Trac:
Username: wagon

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