Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 340
    • Issues 340
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 35
    • Merge requests 35
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • 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
  • #15190
Closed
Open
Issue created Mar 08, 2015 by Damian Johnson@atagar

Is rend-spec's 'service-authentication' a thing?

Hi Nick, on legacy/trac#15004 (closed) I added hidden server descriptor parsing to Stem. donncha has been a fantastic help, providing test data and python crypto examples. Interestingly when we came to the rend-spec's service-authentication lines he wasn't able to find them in the tor codebase.

Were they never implemented? They're very strange fields, prefixing encrypted introduction-points with a plaintext field. Stem presently has (untested) support for them but if they're not actually a thing we should drop them from the spec.

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