linux-kernel - Re: [RFC] make wext wireless bits optional and deprecate them

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]

Date:	Mon, 19 May 2008 14:16:08 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Dan Williams <dcbw@...hat.com>
Cc:	Marcel Holtmann <marcel@...tmann.org>,
	netdev <netdev@...r.kernel.org>, Jean Tourrilhes <jt@....hp.com>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] make wext wireless bits optional and deprecate them


> Instead of testing for wireless/, best thing would probably be to call
> SIOCGIWRANGE on the device and if it returns EOPNOTSUP then it's not
> wireless.  Some drivers may have to load firmware to figure out
> supported rates and encryption capabilities, but to be honest, NM does
> this to detect wireless devices and I haven't run into any issues in 4
> years using it.  If there are issues with drivers, then we need to fix
> the driver too.

I was about to propose calling SIOCGIWNAME since that is what
wireless-tools do and that linux/wireless.h indicates.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)