simon-git: putty (master): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  9fc8320f uxpty: handle $SHELL not being set.
  26930236 Windows Pageant: initial work on deferred decryption.

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:           2020-03-21 16:03:40

commit 9fc8320fc39616e034b6c73cbbb49c9a0c493dfb
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=9fc8320fc39616e034b6c73cbbb49c9a0c493dfb;hp=4fc5d7a5f5528e2f75e781a2fd0a1fd775f53858
Author: Simon Tatham <anakin at pobox.com>
Date:   Sat Mar 21 14:45:03 2020 +0000

    uxpty: handle $SHELL not being set.
    
    This is unlikely in most situations, but 'psusan' in particular is
    intended to be run in a lot of weird environments where things aren't
    properly set up yet. I just found out that if you use a Cygwin-built
    psusan as the proxy process for Windows PuTTY (to get a local Cygwin
    xterm) then it starts up with SHELL unset, and uxpty's forked
    subprocess segfaults when it tries to exec a null pointer.

 unix/uxpty.c | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

commit 26930236ae4aa4b192bb39e481675dd85d885b5e
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=26930236ae4aa4b192bb39e481675dd85d885b5e;hp=9fc8320fc39616e034b6c73cbbb49c9a0c493dfb
Author: Simon Tatham <anakin at pobox.com>
Date:   Sat Mar 21 15:59:51 2020 +0000

    Windows Pageant: initial work on deferred decryption.
    
    This fills in the missing piece of Windows Pageant's story on deferred
    decryption: we now actually know how to put up a dialog box asking for
    the passphrase, when a not-yet-decrypted key is used.
    
    This is quite a rough implementation so far, but it's a start. Known
    issues:
    
     - these new non-modal dialog boxes are serialised with respect to
       each other by the Pageant core, but they can run in parallel with a
       passphrase prompt popping up from the ordinary GUI 'Add Key'
       operation. That may be too confusing; perhaps I should fix it.
    
     - I'm not confident that the passphrase dialog box gets the keyboard
       focus in all situations where I'd like it to (or what I can do
       about it if not).
    
     - the text in the non-modal box has two copies of the instruction
       'enter passphrase for key'.

 windows/winpgnt.c | 134 +++++++++++++++++++++++++++++++++++++-----------------
 1 file changed, 92 insertions(+), 42 deletions(-)