Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C Chutney
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • Chutney
  • Issues
  • #33428

Make chutney check for relay microdescriptors before verifying

In legacy/trac#33232 (moved), we make chutney check for relay and bridge descriptors, and relays in the consensus, before verifying. But we don't check for relay microdescriptors.

The easiest way to check for relay microdescriptors, is using each relay's ed25519 key. In legacy/trac#30642 (moved), we will add an ed25519-identity file to each relay's data directory. Chutney can read the contents of this file, and then search for it in cached-microdescriptors and cached-microdescriptors.new.

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