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
| ||
|
Date: Mon, 16 Sep 2019 12:32:46 +0200 From: Markus Elfring <Markus.Elfring@....de> To: David Miller <davem@...emloft.net>, David Ahern <dsahern@...il.com>, Stephen Hemminger <stephen@...workplumber.org>, netdev@...r.kernel.org Cc: Josh Hunt <johunt@...mai.com>, linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org Subject: Re: ss: Checking selected network ports > If you use netlink operations directly, you can have the kernel filter > on various criteria and only get the socket entries you are interested in. I suggest to take another look at software design options. > This whole discussion has zero to do with what text format 'ss' outputs. Is there a need to improve the software documentation any further? Which programming interface should be used to check the receive queue for a single port (without retrieving more network data before)? Regards, Markus
Powered by blists - more mailing lists