simon-git: putty (pre-0.77): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  18896b66 sshproxy: call backend_unthrottle on unfreeze.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: pre-0.77
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2022-03-30 18:28:59

commit 18896b662e4225b2b2185d49bc916891f1fdbef5
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=18896b662e4225b2b2185d49bc916891f1fdbef5;hp=bdab00341b9e2a48aeb329a40c9a1b8d521ab4a1
Author: Simon Tatham <anakin at pobox.com>
Date:   Wed Mar 30 18:15:43 2022 +0100

    sshproxy: call backend_unthrottle on unfreeze.
    
    If an SSH proxy socket is frozen for long enough, and the SSH server
    continues to send, then sooner or later the proxy SSH connection will
    end up having to freeze its underlying physical socket too. When the
    proxy socket is later unfrozen, it needs to pass that unfreezing on in
    turn.
    
    The way this should happen is that when the SshProxy begins to clear
    the backlog of data passed to it from the proxy SSH connection via
    seat_stdout, it should call backend_unthrottle to inform that proxy
    connection that the backlog is clearing.
    
    But there was no backlog_unthrottle call in the whole of sshproxy.c.
    Now there is.

 proxy/sshproxy.c | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)