Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Arti Arti
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 142
    • Issues 142
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • ArtiArti
  • Issues
  • #230
Closed
Open
Created Nov 11, 2021 by eta@eta💚Maintainer

Halfstream receive window is created afresh after reactor refactor

!126 (merged) broke the previous behaviour of the HalfStream created when a stream is terminated retaining the receive window from when the stream was alive (since the windows are now singlethreaded instead of shared, and shipping the window over to the reactor on closure isn't completely trivial). This means that an attacker could send slightly more data than they should be able to after a stream closes, but it is still bounded (they can't send more than RECV_WINDOW_INIT cells).

We should either fix this, or conclusively determine that it isn't a security risk.

Assignee
Assign to
Time tracking