You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 2, 2022. It is now read-only.
Currently all of the pts will buffer unlimited amounts of data in the tx buffer (bufferevent) of the bottleneck link (Well, it will buffer on the non-bottleneck side as well, but this is unlikely). This is all sorts of bad because it doesn't provide the client/bridge with congestion feedback in the form of a shrinking receive window.
This was skipped in the first pass of the code because obfsproxy does not implement this from what I can tell, even though it should happen for obfs2/3. This probably can wait till after #1 is done, and I would need to ask phw if this is safe to do when I get around to writing code for #2.
The text was updated successfully, but these errors were encountered:
Currently all of the pts will buffer unlimited amounts of data in the tx buffer (bufferevent) of the bottleneck link (Well, it will buffer on the non-bottleneck side as well, but this is unlikely). This is all sorts of bad because it doesn't provide the client/bridge with congestion feedback in the form of a shrinking receive window.
This was skipped in the first pass of the code because obfsproxy does not implement this from what I can tell, even though it should happen for obfs2/3. This probably can wait till after #1 is done, and I would need to ask phw if this is safe to do when I get around to writing code for #2.
The text was updated successfully, but these errors were encountered: