Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #32670

Closed (moved)
(moved)
Open
Created Dec 04, 2019 by Mike Perry@mikeperry

Provide and use higher resolution padding callback timers

During testing, I noticed that the timers.c callbacks could be up to 10 milliseconds late on an otherwise idle Linux laptop tor client. They might be even later on busy relays.

Circuit fingerprinting results may be impacted by this delay. If a deep learning classifier is able to determine padding cells through recognizing this delay, padding will entirely ineffective.

It would be nice to have either high priority timers for things like this, or at least better idle resolution.

We do not yet have enough results to say with certainty if high accuracy padding timers are more important for clients, or for relays.

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