On Tue, 2009-06-09 at 19:48 +0200, gregor kowski wrote: > > Right. But drivers are free to even only _encrypt_ tkip frames and never > > _decrypt_ them after having accepted a hardware key, iow that is > > perfectly valid behaviour and I don't think we should keep uploading the > > key to the driver. Worst case is that the proper upload fails and we > > decrypt all frames in software until the next rollover. > > > What's the point of setting the tkip callback if we aren't interested > in decrypting data by hardware ? Might depend on something else? Anyhow I don't see the point of continuing to call the callback. Maybe it should just be part of the key todo instead when the key is initially uploaded to the hw. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
