linux-kernel - Re: [PATCH] wireless: fix regression caused by regulatory config option

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]

Message-Id: <1225178955.3796.60.camel@johannes.berg>
Date:	Tue, 28 Oct 2008 08:29:15 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	"John W. Linville" <linville@...driver.com>,
	torvalds@...ux-foundation.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, rjw@...k.pl, rodriguez@...eros.com
Subject: Re: [PATCH] wireless: fix regression caused by regulatory config
	option

On Mon, 2008-10-27 at 21:42 +0100, Pavel Machek wrote:

> > > it's not always nice, especially if you're trying to get rid of some
> > > nasty stuff, but think of it this way: you should be able to use a
> > > new kernel on an existing distro, at least for a reasonable type of
> > > distro (eg something shipped in, say, the last 2 years). In this case:
> > > even Fedora 10 is not likely to work!
> > 
> > Well, actually, it _ought_ to work fine, with a smaller set of channels,
> 
> Really? It will still break if your AP uses one of those channels, right?

Well yes, but the driver itself shouldn't simply fail as it did in
Arjan's case, it should just not find the AP rather than saying "sorry,
found error and can't continue" or something like that.

johannes

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