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

Closed (moved)
Open
Opened Mar 15, 2016 by cypherpunks@cypherpunks

timing oracle for rendezvouz circuits

The performance and XMLHTTPRequest javascript APIs provide a toolset sufficient enough to measure for the existence of previously established rendezvous circuits.

Since CORS headers can only be determined after a request is performed, by measuring the time to failure on a series of cross-domain requests and observing the difference between the time-to-failure on the first and subsequent requests we could determine if a user has an already established circuit with a given rendezvous website.

While the timing on performance is quite coarse, it is sufficient to detect the build time of a rendezvous circuit. If the subsequent requests consistently take the same time as the initial request it could be inferred that the user already had a circuit established to the onion address being tested by the XMLHTTPRequest.

The measurement capabilities are very weak given that the sample set of the initial connection can only be 1, as such this attack is not very reliable.

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