simon-git: putty (master): putty.git

[Commits to Tartarus hosted VCS]

TL;DR:
  f049690 Pass -restrict-acl, if given, through to sub-PuTTYs.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: master
Committer:      putty.git
Date:           2017-02-04 08:11:08

commit f049690465b09ac950cbafd5b065bafd968f034b
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=f049690465b09ac950cbafd5b065bafd968f034b;hp=095072fa46b2d7b8beafaddb2f873d2f500a1e10
Author: Simon Tatham <anakin at pobox.com>
Date:   Sat Feb 4 07:57:36 2017 +0000

    Pass -restrict-acl, if given, through to sub-PuTTYs.
    
    This change applies to every situation when GUI PuTTY knowingly spawns
    another GUI PuTTY, to wit, the System menu options 'New Session',
    'Duplicate Session' and the 'Saved Sessions' submenu.
    
    (Literally speaking, what we actually pass through to the sub-PuTTY's
    command line is not the "-restrict-acl" option itself, but a special
    prefix "&R", which has the same meaning but which lives in the special
    pre-argv-splitting command-line namespace like the magic options used
    for Duplicate Session and the old '@sessionname' prefix which the
    Saved Sessions submenu still uses. Otherwise, by the time we split up
    argv and recognised -restrict-acl, it would be too late to parse those
    other options.)
    
    One case in which PuTTY spawns a subprocess and this change _doesn't_
    apply is when the subprocess is a proxy command which happens to be a
    Plink. Recognising Plink commands in that situation would be fragile
    and unreliable, and in any case if the user wants a proxy Plink to be
    ACL-restricted, they are in control of its exact command line so they
    can add -restrict-acl themselves.

 cmdline.c          |  1 +
 windows/window.c   | 42 ++++++++++++++++++++++++++++++------------
 windows/winstuff.h |  1 +
 3 files changed, 32 insertions(+), 12 deletions(-)