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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • #28416

Closed (moved)
Open
Opened Nov 12, 2018 by Iain Learmonth@irl

The ns consensus isn't explicitly ns in the network-status-version line of flavored consensuses

Please review my pull request for torspec:

https://github.com/torproject/torspec/pull/45

tor does not generate ns consensuses that are explicitly labelled as ns consensuses. This updates the spec to make the flavor portion optional, and to allow the assumption to be made that if a flavor is omitted from the "network-status-version" line then it is "ns".

One "flavour" was also turned into a "flavor" for consistency.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.4.0.x-final
Milestone
Tor: 0.4.0.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#28416