From: Michael Buesch <mb@bu3sch.de>
To: Jouni Malinen <j@w1.fi>
Subject: Re: [RFC PATCH 0/7] IEEE 802.11w / management frame protection
Date: Tue, 17 Jun 2008 20:27:50 +0200
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
References: <20080617154008.883383150@localhost> <200806171952.53183.mb@bu3sch.de> <20080617182322.GF4974@jm.kir.nu>
In-Reply-To: <20080617182322.GF4974@jm.kir.nu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Message-Id: <200806172027.50312.mb@bu3sch.de> (sfid-20080617_202816_766412_A001EFD7)
Sender: linux-wireless-owner@vger.kernel.org

On Tuesday 17 June 2008 20:23:22 Jouni Malinen wrote:
> On Tue, Jun 17, 2008 at 07:52:52PM +0200, Michael Buesch wrote:
> 
> > Well, as long as the checksum will fail in that case we're OK for b43,
> > as the driver will notify the need for software crypto for those packets.
> 
> Yes, MIC won't match (or well, in theory it could, but in practice..)
> and if the original frame is available after failed hw-decryption
> attempt, this is indeed all that's needed here. Some hardware designs
> are not able to deliver the unmodified frame due to the way AES hwaccel
> is implemented in them and that gets bit tricky to handle in software
> for IEEE 802.11w.

Yeah I see. Probably need to disable HW crypto for them.
(If firmware modification to pass MGMT frames untouched is impossible)

-- 
Greetings Michael.