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 316
    • Issues 316
    • 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
  • #26925
Closed
Open
Created Jul 25, 2018 by teor@teor

Make link specifier handling in rend-spec-v3 more precise

Split off legacy/trac#26627 (moved).

We should specify that clients and services must not check untrusted link specifiers against the consensus: https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt#n1338 https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt#n1705

Services should also copy unrecognized rend point link specifiers from the introduce cell to the rendezvous join cell. We can copy the text from the service intro->rend spec: https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt#n1705 To the the client desc->intro spec: https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt#n1338

Thanks to catalyst for picking up on these missing parts of the spec.

Edit: fix line numbers

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