netdev - Re: ss command not showing raw sockets? (regression)

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

Date:   Tue, 17 Aug 2021 08:57:10 -0600
From:   David Ahern <dsahern@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>, Jonas Bechtel <post@...chtel.de>
Cc:     netdev@...r.kernel.org
Subject: Re: ss command not showing raw sockets? (regression)

On 8/16/21 4:08 PM, Jakub Kicinski wrote:
> On Sun, 15 Aug 2021 23:17:38 +0200 Jonas Bechtel wrote:
>> I've got following installation:
>> * ping 32 bit version
>> * Linux 4.4.0 x86_64 (yes, somewhat ancient)
>> * iproute2  4.9.0 or 4.20.0 or 5.10.0
>>
>> With one ping command active, there are two raw sockets on my system:
>> one for IPv4 and one for IPv6 (just one of those is used).
>>
>> My problem is that
>>
>> ss -awp
>>
>> shows 
>> * two raw sockets (4.9.0)
>> * any raw socket = bug (4.20.0)
>> * any raw socket = bug (5.10.0)
> 
> Could you clarify how the bug manifests itself? Does ss crash?

I take it kernel version is constant and iproute2 version changes,
correct? Can you download the source and do a git bisect?

> 
>> So is this a bug or is this wont-fix (then, if it is related to
>> kernel version, package maintainers may be interested)?