linux-kernel - Re: [PATCH 09/15] rfkill: add the WWAN radio type

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:	Tue, 20 May 2008 22:12:57 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Ivo van Doorn <ivdoorn@...il.com>
Cc:	linux-kernel@...r.kernel.org, Thomas Renninger <trenn@...e.de>,
	Inaky Perez-Gonzalez <inaky@...ux.intel.com>,
	Iñaky Pérez-González 
	<inaky.perez-gonzalez@...el.com>,
	"John W. Linville" <linville@...driver.com>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH 09/15] rfkill: add the WWAN radio type

On Tue, 20 May 2008, Ivo van Doorn wrote:
> On Sunday 18 May 2008, Henrique de Moraes Holschuh wrote:
> > Unfortunately, instead of adding a generic Wireless WAN type, a technology-
> > specific type (WiMAX) was added.  That's useless for other WWAN devices,
> > such as EDGE, UMTS, X-RTT and other such radios.
> > 
> > Add a WWAN rfkill type for generic wireless WAN devices.  No keys are added
> > as most devices really want to use KEY_WLAN for WWAN control (in a cycle of
> > none, WLAN, WWAN, WLAN+WWAN) and need no specific keycode added.
> >
> > Signed-off-by: Inaky Perez-Gonzalez <inaky@...ux.intel.com>
> 
> If WiMAX is a subset of the WWAN technology, shouldn't we replace WiMAX completely
> in rfkill? Otherwise people might get ideas and add the other technologies seperately as well. ;)
> 
> Other then that, the addition of WWAN is fine with me. :)

Actually, I have no reason to believe there *isn't* a device with
KEY_WIMAX... but we need the WWAN type before we bother with a WiMax
type :-)

IMO, we should fix the issue by adding a "supertype", i.e., a class.
Use that for generic grouping, and let type be more specific when there
is a reason for it.  Repeat the class as the type to get a "generic"
type, when there is no reason to bother with more specific types.

Stuff like "WiMax", "802.1a", "EDGE", "GRPS", "802.1bg" would be the
type, and class would be "WLAN", "WWAN", etc.

We would only deal with classes on rfkill-input.  Anything else more
specific should be done in userspace instead, disabling rfkill-input.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/