Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 832
    • Issues 832
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #16562

Closed
Open
Created Jul 12, 2015 by Nick Mathewson@nickm🏃Owner

Harmonize curve25519-signature format with what others are doing

Here's another one that we have to do before the 0.2.7.2-alpha release if we're going to do it at all:

https://github.com/trevp/tswip/blob/master/curve25519sigs.md

I'm not in love with the differences here, but they seem mostly harmless. Trevor tells me that there's a chance of his that format being standardized. If so, we might as well help it along by doing what they do.

Changing the nonce-generation mechanism is IMO not very important. The change to consider before the next alpha would be the signature format.

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