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

Closed (moved)
(moved)
Open
Created Jun 03, 2018 by Isis Lovecruft@isis

find all instances of SHA-1 in our design and implementation and kill them with fire

This is a parent ticket for finding every use of SHA-1 in our specs/design and code, detailing it, and coming up with a plan to replace it.

From the Seattle notes, we use truncated SHA-1 in v2 onion services and relay_crypt_one_payload(), and we use full width SHA-1 for relay fingerprints and, again, v2 onion services. Nick has also written a draft document detailing where we use SHA-1, however it is presently outdated and incorrect in some places.

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