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

Closed (moved)
Open
Opened Nov 22, 2016 by George Kadianakis@asn

prop224: Implement stealth client authorization

prop224 currently does not specify stealth client authorization.

This is a feature from rend-spec.txt which makes the HS create a unique onion address for each authorized client. This way revoked clients cannot get presense information about the hidden service, since they don't know the onion addresses of other clients.

This is useful for cases where authorized clients have a chance of turning adversarial and there is a need for total revocation.

tl;dr: We need to specify stealth auth in prop224, and implement it.

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#20742