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 311
    • Issues 311
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • 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
  • #40124
Closed
Open
Created Sep 15, 2020 by Nick Mathewson@nickm🎨Owner

Incorrect key ID type used in some ed25519 certificates

In cert-spec.txt we specify several possible values for the CERT_KEY_TYPE field, in section A.4. But we don't actually use those: everywhere that we call tor_cert_sign_impl() , signed_key type is set to SIGNED_KEY_TYPE_ED25519.

We should adjust the spec to clarify that current tor implementations behave, and (assuming it won't introduce compatibility issue) adjust Tor relay behavior to conform to the spec. We should probably leave onion service behavior alone.

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