Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor Specifications
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

  • The Tor Project
  • Core
  • Tor Specifications
  • Issues
  • #36

Closed
Open
Opened Jan 24, 2021 by Matthew Finkel@sysrqb

Should the v3 rend spec be the new 'rend-spec'?

On spec.torproject.org there is a link for /rend-spec-v2, /rend-spec-v3, and /rend-spec. Currently, rend-spec redirects to the same page as rend-spec-v2, but with v2 deprecation coming sometime this year pointing rend-spec at rend-spec-v3 may be more beneficial.

One example of a reason we may want to change this mapping is because RFC 7686 references /rend-spec. We want new adoption of onion services to reference the correct protocol, such as certificate authorities issuing TLS certificates with .onion addresses. I heard adjusting the mapping may help with this adoption in the future (or prevent some confusion, at least).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/torspec#36