On Thu, 2009-02-05 at 14:07 +0200, Jouni Malinen wrote: > (a) Currently not, but once people realize that the length field has a > maximum value of 65535, using it as the largest attempt sounds like the > most logical choice. In other words, yes, this will require a small > change in programs that care (wpa_supplicant, which I already changed; > iwlist; etc.), but the change is minimal and not doing this does not break > anything new. True. > (b) Yes, user space apps better be prepared to read the results even if > the last entry is truncated (can happen with current kernel). There is > no clear way for the app to know that there could be more scan results > (well, it could guess that this is the case if the returned buffer is > very close to 64 kB), but it is not like scanning is that reliable > operation anyway, so applications better be prepared to not always > find every BSS in the results. Yeah, the truncation is a little worrying. I doubt any program but wpa_supplicant is prepared to handle that. Should we completely remove the entry, and add some new/custom piece to stream that indicates that we had to truncate here? johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
