simon-git: putty (master): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  57c45c62 Uppity: print a startup message.
  4135e5d2 pscp: clear act->buf after receiving 'T' command.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: master
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2019-05-09 23:50:13

commit 57c45c620f97e0db81b83754214267f689932d0e
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=57c45c620f97e0db81b83754214267f689932d0e;hp=1d733808c3182ddcdb02af1b2e2c3c0f282ef28a
Author: Simon Tatham <anakin at pobox.com>
Date:   Wed May 8 08:26:09 2019 +0100

    Uppity: print a startup message.
    
    When I start Uppity in listening mode, it's useful to have it
    acknowledge that it _has_ started up in that mode, and isn't (for
    example) stuck somewhere in my local wrapper script.

 unix/uxserver.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

commit 4135e5d29550654227e275907e63a58e232cce38
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=4135e5d29550654227e275907e63a58e232cce38;hp=57c45c620f97e0db81b83754214267f689932d0e
Author: Simon Tatham <anakin at pobox.com>
Date:   Wed May 8 08:30:10 2019 +0100

    pscp: clear act->buf after receiving 'T' command.
    
    Without this missing line, if you tried to download a file in SCP mode
    using the -p option, the payload of the 'T' command (file times) would
    still be sitting in act->buf when we went back round the loop, so the
    payload of the followup 'C' or 'D' would be appended to it, leading to
    a massive misparse and a complaint about illegal file renaming.

 pscp.c | 1 +
 1 file changed, 1 insertion(+)