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

Closed
Open
Opened Mar 01, 2012 by Mike Perry@mikeperry

Randomize non-pipelined requests to defend against traffic fingerprinting

According to Martin Henze (who works with Andriy Panchenko), the defense in #3914 (closed) is inadequate due to the fact that many sites forcibly disable pipelining.

He implemented a defense that randomizes non-pipelined HTTP requests as well, but it may need some cleanup. It also needs testing against their framework still, I believe.

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