Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #26925

Closed (moved)
Open
Opened Jul 25, 2018 by teor@teor

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

Split off #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
Tor: 0.3.5.x-final
Milestone
Tor: 0.3.5.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#26925