On Tue, 2008-06-17 at 19:52 +0200, Michael Buesch wrote: > On Tuesday 17 June 2008 19:47:49 Jouni Malinen wrote: > > On Tue, Jun 17, 2008 at 06:44:27PM +0200, Johannes Berg wrote: > > > > > > crypto. It is unclear whether this can be used as-is with devices that > > > > use hwaccel for crypto at least before the low-level drivers and/or > > > > firmware have been modified to cope with the possibility of CCMP being > > > > used with management frames. > > > > > > b43 will be able to do this for sure, it doesn't care what sort of frame > > > is encrypted. The question is how drivers can indicate > > > support/non-support I guess. > > > > One of the problems is that CCMP as defined in IEEE 802.11i for data > > frames is not compatible with CCMP as defined in IEEE 802.11w for > > management frames (there are small differences in AAD and nonce > > generation). As such, if the hardware/firmware is trying to decrypt > > received CCMP protected frames based on the IEEE 802.11i rules even if > > the frame is a management frame, the end result is not going to be very > > good.. Oh, ok, never mind then. Probably not worth accelerating anyway. > 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. I don't think it'll try to decrypt them anyway but I thought we could at least use it to encrypt. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part