Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #3914
Closed
Open
Created Sep 03, 2011 by Mike Perry@mikeperry

Experimental website traffic fingerprinting defense

For grins, I decided to make an experimental fingerprinting defense to defend against http://lorre.uni.lu/~andriy/papers/acmccs-wpes11-fingerprinting.pdf.

Basically the defense is to enable HTTP pipelining and to randomize the size and the order of the pipeline queue for each connection. It's easy to do and doesn't cost us any overhead.

I think we should ask the researchers to test it out for us or give us their source code.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking