lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171023144142.7496e791@shemminger-XPS-13-9360>
Date:   Mon, 23 Oct 2017 14:41:42 +0200
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Phil Sutter <phil@....cc>
Cc:     netdev@...r.kernel.org, Humberto Alves <hjalves@...e.com>,
        Eric Dumazet <eric.dumazet@...il.com>
Subject: Re: [iproute PATCH] ss: Distinguish between IPv4 and IPv6 wildcard
 sockets

On Wed, 18 Oct 2017 19:58:13 +0200
Phil Sutter <phil@....cc> wrote:

> Commit aba9c23a6e1cb ("ss: enclose IPv6 address in brackets") unified
> display of wildcard sockets in IPv4 and IPv6 to print the unspecified
> address as '*'. Users then complained that they can't distinguish
> between address families anymore, so change this again to what Stephen
> Hemminger suggested:
> 
> | *:80    << both IPV6 and IPV4
> | [::]:80 << IPV6_ONLY
> | 0.0.0.0:80  << IPV4_ONLY
> 
> Note that on older kernels which don't support INET_DIAG_SKV6ONLY
> attribute, pure IPv6 sockets will still show as '*'.
> 
> Cc: Humberto Alves <hjalves@...e.com>
> Cc: Eric Dumazet <eric.dumazet@...il.com>
> Signed-off-by: Phil Sutter <phil@....cc>

Applied both.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ