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

[Commits to Tartarus hosted VCS]

TL;DR:
  fdfad6ad Fix accidental change to connshare pipe naming.
  f4d99d3f Docs updates.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: pre-0.75
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2021-05-02 09:17:19

commit fdfad6adca248ed56d1f32e0f1d0d853e78f2c3b
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=fdfad6adca248ed56d1f32e0f1d0d853e78f2c3b;hp=f3ee4dbe20cc935edc78d2fcdd37c24130f62e86
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun May 2 07:55:15 2021 +0100

    Fix accidental change to connshare pipe naming.
    
    Jacob spots that on Windows, current PuTTY is not compatible with
    0.74, if one of them acts as a connection sharing upstream and the
    other as a downstream. That's because commit 1344d4d1cd84b58
    accidentally changed the hash preimage in capi_obfuscate_string() so
    that it no longer had an SSH-like string length field at the front. So
    the two versions of PuTTY will expect the named pipe to have a
    different pathname, and so they won't be able to find each other.
    
    Interoperation between PuTTY versions is not the most important use
    case of connection sharing - surely the typical user will invoke it by
    activating the same session twice, or by using Duplicate Session. But
    it was never intended to deliberately _not_ work, so let's fix it
    before 0.75 goes out, so that at least the incompatible behaviour will
    only ever have appeared in development snapshots.

 windows/wincapi.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

commit f4d99d3f598b39e373544861725dd1afcfd4bb9a
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=f4d99d3f598b39e373544861725dd1afcfd4bb9a;hp=fdfad6adca248ed56d1f32e0f1d0d853e78f2c3b
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Apr 18 17:03:01 2021 +0100

    Docs updates.
    
    Since the previous commit is causing an RC2 build of 0.75 anyway,
    let's take the opportunity to bring in updates to the docs from main,
    so that the release will have the most up-to-date version available.
    
    This is a combined cherry-pick of:
      f6142ba29b9398d03ad56b5e2db03c5ec9fcba44
      7c1bea59a3b49853808f96743a7464fb99ee1e2d
      f5d1d4ce4b1f54476d9603215345cd43f1e465c7

 doc/faq.but    | 10 ++++++++++
 doc/pubkey.but |  2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)