Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #40071
Closed (moved) (moved)
Open
Created Mar 03, 2021 by juga@jugaMaintainer

Add KeyValue with the name of the dirauth

We've mentioned this several times, when searching for bugs: it would be easier to find out from which bwauth an archived Bandwidth File has been generated if it would be included in the file itself.

Currently it's only possible to correlate the hash of the file with the dirauth in the vote. Or guess it by the size of the file and the time it has been published, but it's just a guess.

This has also be commented in /tpo/metrics/collector#33061.

It also have more sense than having an scanner nickname.

Assignee
Assign to
Time tracking