| 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
| ||
|
Message-Id: <1238071318.8206.18.camel@localhost.localdomain> Date: Thu, 26 Mar 2009 13:41:58 +0100 From: Marcel Holtmann <marcel@...tmann.org> To: netdev@...r.kernel.org Subject: Creating an Ethernet subtype setting Hi guys, so we have more and more subsystem that expose themselves as Ethernet networking devices and it really becomes hard to identify them in an easy way. For example WiFi has been an Ethernet device since a long time now and distinguishing between Ethernet and WiFi is not that hard since we have the good old WEXT ioctls to identify WiFi devices. However with WiMAX, Bluetooth, GSM/CDMA modems and even Ethernet bridge devices, it would be nice to have an easy way to identify them. Since it has become a mess for laptops that include 4 or more different technologies. For most of these Ethernet devices, we have to either connect first or authenticate or do something via a control channel to make them work. So it would be nice to have an easy way to identify them. I was thinking about doing this on a per driver or subsystem level and just setting a subtype value that is Linux specific. We could then expose this via sysfs and HAL, DeviceKit and udev could use it to annotate these devices correctly. Is this is a good idea or totally stupid and should be done better on a different level? Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists