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

Message-ID: <AM4PR0901MB1252D66A440ACA247AD32DF4CC4D0@AM4PR0901MB1252.eurprd09.prod.outlook.com>
Date:   Wed, 18 Oct 2017 14:08:48 +0000
From:   Humberto Alves <hjalves@...e.com>
To:     Stephen Hemminger <stephen@...workplumber.org>,
        Eric Dumazet <eric.dumazet@...il.com>
CC:     Phil Sutter <phil@....cc>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [iproute2] regression in ss output

Looks perfect to me. Thanks!

On 10/17/2017 03:49 AM, 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
> 


Download attachment "smime.p7s" of type "application/pkcs7-signature" (3984 bytes)