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

Closed (moved)
Open
Opened Jan 11, 2019 by s7r@s7r🏁

prop224: Implement offline keys for v3 onion services

Prop224 is designed to support offline master keys for v3 onion services, a great functionality that has many advantages and becomes more and more discussed in threat models. Logging this ticket now to keep track of it, even if it's not urgent at the moment.

This is what seams to be needed at first look (might end up as child tickets to this one):

  1. Implement temporary keys + certificates signed by master onion service key with limited validity for v3 onion services.

  2. Implement a small utility tool in Tor so that users can create such onion service keys offline, similar to tor --keygen for relays, with a secondary argument of --keylifetime which defaults to 30 days but can be changed to any value user prefers.

  3. Implement torrc option HiddenServiceOfflineKey 0|1 (that defaults to 0) so Tor will know it must not try to generate the onion service master key if missing from disk, or even look for it.

Most of the logic and behavior from ed25519 offline master key for relays should be applied at these first 3 points as well.

  1. Implement mnemonic seed backup for onion service master key, so the same private key can be restored using a string of words that produce the same parameters for the curve. This is simple and widely tested/implemented for secp256k1, and implementing for our needs and threat model is simple and totally worth it from user experience perspective.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#29054