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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 19 Sep 2011 21:44:33 +0100
From:	Dave Kilroy <kilroyd@...glemail.com>
To:	Valdis.Kletnieks@...edu
CC:	linux-kernel@...r.kernel.org, greg@...ah.com, pe1dnn@...at.org
Subject: Re: [PATCH 3/3] staging: wlags49_h2: Declare support for WEXT 21

On 19/09/2011 21:22, Valdis.Kletnieks@...edu wrote:
> On Mon, 19 Sep 2011 21:08:16 BST, David Kilroy said:
>> There may be a few areas where we don't actually support WE21,
>> but by doing this it will make it easier to find those places.
>
> I'll bite - what happens when we find such a place?  Kernel fails to build, or
> user has a suboptimal usage experience, or?

The user would have a sub-optimal experience. iwconfig may not display a 
few things correctly (ESSID?) in particular scenarios.

The reason I included this patch was that I'm not sure whether 
wpa-supplicant requires WEXT version to be above a certain threshold to 
use the events in the previous patch. I'm happy to drop this one if it 
just works.

> What are the expected chances that sticking this in linux-next for a cycle will
> result in most/all of the places being found before this all appears in an
> official release?  I'm thinking this should probably go in linux-next right after
> the next merge window closes, to maximize the chances we'll shake it
> all out during almost 2 cycles before it hits the streets. (And yes, I know
> it's a staging/ driver - if somebody else says "one cycle is more than enough"
> I'm OK with that too...)

This hardware is old, and as far as I can tell quite rare. I'd hope we 
can get some feedback from Henk on the series before applying this patch.

Thanks,

Dave.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ