Working on wireless improvements
Details
Sat, Jun 1
add the modules Makefile
Fri, May 31
Thu, May 30
The real problem isn't the ABI key size, it's that the current net80211 API routine expects the ioctl size is fixed. If that size check wasn't there and we relied on the key request key size and verified it fit inside the ioctl buffer size then we'd be fine.
Wed, May 29
Thu, May 23
Would nv lists be better?
Wed, May 22
Sat, May 18
Tue, May 14
Mon, May 13
I see you made comments of "ieee80211_set_software_ciphers() is not needed" in if_rtwn.c. Do you mind to add it in the rest of the drivers files? Or is there any better/central place to put such comment or document it?
Sun, May 12
remove the VAP keymgmt flags for now; will reintroduce it and change the
ioctl API to use that instead when it's necessary.
remove NONE, from bz@
Thu, May 9
May 3 2024
OK, I rebuilt world and found where this breaks userland.
May 2 2024
Is there any implementation for these new functions, i.e., something which updates the drivers or is this just dead wood swimming down the river?
Would be great if the commit message would mention IEEE80211_CRYPTO_MODULE() somehow so one can find this in the future more easily.
In theory I am fine with this once these modules actually exist. I would also fantastic if the annoying printf instead of loading them could be fixed. reverse order.
Most of the comments were marked "done" and changed some since the original comments but the "RSN AKM suite element" table still has a mix of #define suffixes and comments for the "256" cases? Is this on purpose for some reason beyond this file? At least the TDLS case I had originally asked for _256? I just wonder why not? Can you explain?
This still has changes not marked "done".
Is there a change in the stack which does change the drivers to use this?
You didn't answer my previous question?
Can you please update the commit message? Apart from that it seems fine-ish with what cc@ said.
Individual accept.
May 1 2024
address comments from cc@