On Wed, 2007-03-28 at 12:00 -0700, Jouni Malinen wrote: > Use of WPA/RSN IE vs. individual parameters depends on the driver. For > example, NDIS drivers generate the IEs internally and need to be > configured with the key management (WPA-PSK, WPA-Enterprise, WPA2-PSK, > WPA2-Enterprise, ..) and cipher suites separately. They would not use > WPA/RSN IE at all. Some drivers use the IE so that kernel code does not > need to have all the code for generating it. They may (or may not, > depending on needs) ignore the individual values. Yes, I know that much. > > I'm inclined to just require userspace to put both the IE and the > > individual settings into the relevant nl80211 messages, but then we > > might just as well piece the IE together from those settings, no? > > As long as the information is available for the driver at the time of > association request, it does not really matter how that information got > there.. I'd have thought you would rather see the IE included to be able to experiment with new things easier ;) I really can't decide which way to use. Piecing together the IE in the kernel and then just passing it doesn't seem like much overhead, but doing it in userspace gives us more freedom for experiments... johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
