Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #2768

Closed (moved)
Open
Opened Mar 16, 2011 by Robert Ransom@rransom

Write standalone directory document signature verification tools

Right now, the only easy way for researchers to verify that they are using the actual Tor network consensuses/votes/descriptors is to verify Karsten's OpenPGP signature of the tarball (if there is one). Tor already contains code to verify those documents which have signatures; we should expose that code to researchers' scripts, too.

The extra-info descriptors and microdescriptors are authenticated by having their hashes published in other documents, rather than being signed directly, so they will be a bit trickier for simple tools to verify; we should postpone writing verification tools for those documents for now.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#2768