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
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

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

Closed (moved)
Open
Opened Sep 13, 2018 by Mike Perry@mikeperry

Emit CIRC_BW event early for dropped cells

While reviewing the dropmark paper (https://petsymposium.org/2018/files/papers/issue2/popets-2018-0011.pdf) and asking the authors to test it against vanguards's dropped cell detection, I realized that since we only normally emit CIRC_BW events once per second, the attack may still have enough time succeed against vanguards.

The fix is to emit the CIRC_BW event as soon as we get a relay cell that does not cause us to update our delivered or overhead byte counts. It's pretty simply to do this. Patch incoming.

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