| 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: <20080918134112.GB4552@tuxdriver.com> Date: Thu, 18 Sep 2008 09:41:13 -0400 From: "John W. Linville" <linville@...driver.com> To: David Miller <davem@...emloft.net> Cc: j@...fi, jouni.malinen@...eros.com, alex.williamson@...com, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [GIT]: Networking (WEXT events and 64/32 compat) On Wed, Sep 17, 2008 at 01:11:33PM -0700, David Miller wrote: > From: Jouni Malinen <j@...fi> > Date: Wed, 17 Sep 2008 12:11:28 -0700 > > > Would it be acceptable to ever enable use of IWEVASSOCREQIE / > > IWEVSSOCRESPIE in kernel if the workaround were available in new > > wpa_supplicant versions? Or should we try to add a new WEXT event > > type that uses fixed size for the length field and then replace the old > > IWEVCUSTOM with the new type since IWEVCUSTOM does not work with > > 64/32-bit case (wpa_supplicant just knows how to avoid processing that > > bogus event data)? > > Moving to a new event with a strictly sized datastructure, instead of > one that has variable sized members like pointers and crap which are > impossible to compat layer'ify, is indeed my preference. > > But in that case, we might as well make nl80211 usable instead. This is, of course, my opinion as well. John -- John W. Linville linville@...driver.com -- 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/
Powered by blists - more mailing lists