simon-git: putty (master): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  71a3e7da host_strduptrim: support RFC 4007 address literals.

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-03-09 09:40:10

commit 71a3e7da9e9b1fc0e95c9d4e02a63fb1c3eed57e
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=71a3e7da9e9b1fc0e95c9d4e02a63fb1c3eed57e;hp=d2ddb2fdf4f4c0152c9c67425af3c50c80dcf39a
Author: Simon Tatham <anakin at pobox.com>
Date:   Sat Mar 9 08:10:02 2019 +0000

    host_strduptrim: support RFC 4007 address literals.
    
    I'd never even heard of these before. We don't need to do anything
    unusual with these when passing them to our own getaddrinfo, but
    host_strduptrim considered them a violation of its expectations about
    what an IPv6 literal looked like, and hence wasn't stripping square
    brackets off one. So a port-forwarding command-line option such as
    '-L 12345:[fe80::%eth0]:22' would cause the address string in the
    direct-tcpip CHANNEL_OPEN packet to be "[fe80::%eth0]" instead of the
    correct "fe80::%eth0", leading to getaddrinfo failure on the SSH
    server side.

 utils.c | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)