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

Closed (moved)
Open
Opened May 10, 2016 by David Goulet@dgoulet😈

prop224: Refactor rend_data_t so be able to use multiple HS version

Break rend_data_t into something that could looks like this (or maybe without a union...):

struct rend_data_t {
  uint32_t version; /* XXX: Maybe not necessary if our code flow doesn't
                     * require us to learn the version through that data struct. */
  union {
    hs_data_v2_t v2;
    hs_data_v3_t v3;
  } hs;
};

Once we have such construction, we can use v3 with that data structure more cleanly.

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