Re: [PATCH] mesh: fix off-by-one in buf length calculation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 23, 2018 at 10:15:42AM -0500, Bob Copeland wrote:
> The maximum size of a Mesh Peering Management element in the case
> of an AMPE close frame is actually 24 bytes, not 23 bytes, plus the
> two bytes of the IE header (802.11-2016 9.4.2.102).  Found by
> inspection.

Thanks, applied. Also the first two octets of the payload (Category and
Action fields) were missing from the size, so I added them as well. It
did not look like the maximum length could really be reached in
practice, though, due to extra room allocated for the other elements.
 
-- 
Jouni Malinen                                            PGP id EFC895FA

_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux