Kristof Provost 00eab743ab pf: Fix possible incorrect IPv6 fragmentation ... When forwarding pf tracks the size of the largest fragment in a fragmented packet, and refragments based on this size. It failed to ensure that this size was a multiple of 8 (as is required for all but the last fragment), so it could end up generating incorrect fragments. For example, if we received an 8 byte and 12 byte fragment pf would emit a first fragment with 12 bytes of payload and the final fragment would claim to be at offset 8 (not 12). We now assert that the fragment size is a multiple of 8 in ip6_fragment(), so other users won't make the same mistake. Reported by: Antonios Atlasis <aatlasis at secfu net> MFC after: 3 days		2017-04-20 09:05:53 +00:00
..
ipfw	Avoid undefined behavior.	2017-04-14 11:58:41 +00:00
pf	pf: Fix possible incorrect IPv6 fragmentation	2017-04-20 09:05:53 +00:00