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]

Message-ID: <20210816150800.28ef2e7c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Mon, 16 Aug 2021 15:08:00 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Jonas Bechtel <post@...chtel.de>
Cc:     netdev@...r.kernel.org
Subject: Re: ss command not showing raw sockets? (regression)

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?

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