netdev - Bug in netlink monitor

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]

Date:   Tue, 25 Oct 2022 14:18:00 +0300
From:   George Shuklin <george.shuklin@...il.com>
To:     netdev@...r.kernel.org
Subject: Bug in netlink monitor

I found that if veth interface is created in a namespace using netns 
option for ip, no events are logged in `ip monitor all-nsid`.

Steps to reproduce:

(console1)

ip monitor all-nsid

(console 2)

ip net add foobar

ip link add netns foobar type veth

Expected results:

Output in `ip monitor`. Actual result: no output, (but there are two new 
veth interaces in foobar namespace).

Additional observation: namespace 'foobar' does not have id in output of 
`ip net`:

# ip net
foobar
test (id: 0)
test2 (id: 1)