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] [day] [month] [year] [list]

Message-Id: <1211405864.3698.7.camel@johannes.berg>
Date:	Wed, 21 May 2008 23:37:44 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	"John W. Linville" <linville@...driver.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


> > I have filed a patch to fix HAL to use the canonical SIOCGIWNAME at
> > https://bugs.freedesktop.org/show_bug.cgi?id=16037. Any further
> > objections to this patch?
> 
> I think this is going to fall under the "userland ABI" category.
> We can make it a configurable option, but I don't think we are free
> to remove it completely since there is at least existing versions of
> HAL that use it.

Well, yes, I gave it a year in the feature removal schedule since I
thought nobody was actually using it. But if you look at how hal/sysfs
are always dependent on new versions of each other *anyway*, I think we
can get away with removing this in maybe two years time, and
distributors can unset the option if they know their hal is new enough?

johannes

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