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: Tue, 3 Apr 2018 19:04:26 -0600 From: David Ahern <dsahern@...il.com> To: Jiri Pirko <jiri@...nulli.us> Cc: Si-Wei Liu <si-wei.liu@...cle.com>, mst@...hat.com, stephen@...workplumber.org, alexander.h.duyck@...el.com, davem@...emloft.net, jesse.brandeburg@...el.com, kubakici@...pl, jasowang@...hat.com, sridhar.samudrala@...el.com, netdev@...r.kernel.org, virtualization@...ts.linux-foundation.org, virtio-dev@...ts.oasis-open.org Subject: Re: [RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice On 4/3/18 9:42 AM, Jiri Pirko wrote: >> >> There are other use cases that want to hide a device from userspace. I > > What usecases do you have in mind? As mentioned in a previous response some kernel drivers create control netdevs. Just as in this case users should not be mucking with it, and S/W like lldpd should ignore it. > >> would prefer a better solution than playing games with name prefixes and >> one that includes an API for users to list all devices -- even ones >> hidden by default. > > Netdevice hiding feels a bit scarry for me. This smells like a workaround > for userspace issues. Why can't the netdevice be visible always and > userspace would know what is it and what should it do with it? > > Once we start with hiding, there are other things related to that which > appear. Like who can see what, levels of visibility etc... > I would not advocate for any API that does not allow users to have full introspection. The intent is to hide the netdev by default but have an option to see it.
Powered by blists - more mailing lists