Page MenuHomeFreeBSD

[net80211] handle hardware encryption offload in the receive path
ClosedPublic

Authored by adrian on Nov 15 2016, 9:49 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 2, 7:43 PM
Unknown Object (File)
Tue, Apr 2, 5:57 PM
Unknown Object (File)
Mar 3 2024, 7:33 AM
Unknown Object (File)
Mar 3 2024, 7:06 AM
Unknown Object (File)
Jan 9 2024, 5:59 AM
Unknown Object (File)
Jan 9 2024, 5:59 AM
Unknown Object (File)
Jan 9 2024, 5:59 AM
Unknown Object (File)
Jan 9 2024, 4:52 AM
Subscribers

Details

Summary
  • teach the crypto modules about receive offload - although I have to do some further reviewing in places where we /can't/ have an RX key
  • teach the RX data path about receive offload encryption - check the flag, handle NULL key, do decap and checking as appropriate.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

adrian retitled this revision from to [net80211] handle hardware encryption offload in the receive path.
adrian updated this object.
adrian edited the test plan for this revision. (Show Details)
avos edited edge metadata.
avos added inline comments.
sys/net80211/ieee80211_crypto.c
600 ↗(On Diff #22232)

some hardware can pass h/w key index - does it needed here?

sys/net80211/ieee80211_sta.c
748 ↗(On Diff #22232)

here too

This revision is now accepted and ready to land.Nov 15 2016, 11:56 PM
sys/net80211/ieee80211_crypto.c
600 ↗(On Diff #22232)

Sure, but if we get a hardware key but it strips the IV, we still can't really check anything. :(

This revision was automatically updated to reflect the committed changes.