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

Closed (moved)
(moved)
Open
Created Oct 17, 2018 by Taylor Yu@catalyst

dirauth key pinning can be bypassed sometimes?

It looks like sometimes key pinning can be bypassed. One example is in #27800 (moved), where it seems that an ed25519 key got shared between two relays (Or maybe that's two iterations of the same relay, where the operator rolled the RSA key but not the ed25519 key.)

Fixing this the "right" way might involve keeping multiple versions of a relay descriptor around, with metadata about which vote or consensus it goes with.

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