netdev - Re: [iproute2] regression in ss output

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>] [day] [month] [year] [list]

Date:   Wed, 18 Oct 2017 19:11:16 +0200
From:   Phil Sutter <phil@....cc>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     Eric Dumazet <eric.dumazet@...il.com>,
        Humberto Alves <hjalves@...e.com>, netdev@...r.kernel.org
Subject: Re: [iproute2] regression in ss output

On Mon, Oct 16, 2017 at 07:49:58PM -0700, Stephen Hemminger wrote:
> On Mon, 16 Oct 2017 19:00:36 -0700
> Eric Dumazet <eric.dumazet@...il.com> wrote:
> 
> > On Mon, 2017-10-16 at 14:28 -0700, Stephen Hemminger wrote:
> > > On Mon, 16 Oct 2017 20:44:07 +0000
> > > Humberto Alves <hjalves@...e.com> wrote:
> > >   
> > > > Yes, just get rid of this 'if statement'.
> > > > in6addr_any should be represented as '::', not '*'. Otherwise it's 
> > > > impossible to distinguish IPv4 listening addresses from IPv6. Thank you :)  
> > > 
> > > But IPv6 accepts IPv4 as well.  
> > 
> > Not always (IPV6_V6ONLY socket option)
> > 
> > I agree that this recent change in ss is problematic.
> > 
> > Please give us back a way to distinguish IPV6 and IPv4
> 
> What about
> 	*:80	<< both IPV6 and IPV4
> 	[::]:80	<< IPV6_ONLY
> 	0.0.0.0:80  << IPV4_ONLY

Assuming that this will be distinguished based on INET_DIAG_SKV6ONLY
attribute, tc will then use the asterisk for v6only sockets on older
kernels not supporting the feature.

Fine with me, just a heads-up!

Cheers, Phil