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

Closed (moved)
(moved)
Open
Created Jan 08, 2014 by cypherpunks@cypherpunks

connection_bucket_write_limit reveals used link protocol

Plain text of TLS record can't be more than 16384 bytes. Tor before v4 link protocol used 512 bytes cells. connection_bucket_write_limit allows to flush not more than 32 cells. That was 16K limit exactly. With v4 size of cells changed, now it's 514 bytes, and connection_bucket_write_limit allows to flush 32 cells still that in result more than 16Kbytes. Passive adversary can to detect used protocol, and openssl can to create two records per one flush while second record contains not so much actual bytes.

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