tcpdump/tests/hncp_dhcpv6data-oobr.out

    1  06:19:57.131076 IP6 (flowlabel 0x01cc3, hlim 234, next-header UDP (17) payload length: 11025) 400::e4ff:ffff:adf9:8900:0.1646 > 62:9de3:ff47:ebec:8206:ff00:ad:ff00.8231: hncp (11017)
	Future use: type=16384 (5)
	DHCPv6-Data (25)
		Unknown (4)
		Unknown (4)
		SNTP-servers (61956) (invalid)
	 [|hncp]
Use UTC/GMT time when building/checking tests files This will avoid some differences when checking in different time zones. We now run the tests without the '-t' option. This will allow to get problems/changes in time printing functions. Update the output of the tests accordingly. Moreover: Add the '-#' option to better identify a packet when there is a difference in output. 2018-08-04 14:46:17 +08:00			`1 06:19:57.131076 IP6 (flowlabel 0x01cc3, hlim 234, next-header UDP (17) payload length: 11025) 400::e4ff:ffff:adf9:8900:0.1646 > 62:9de3:ff47:ebec:8206:ff00:ad:ff00.8231: hncp (11017)`
CVE-2017-13042/HNCP: add DHCPv6-Data bounds checks hncp_print_rec() validates each HNCP TLV to be within the declared as well as the on-the-wire packet space. However, dhcpv6_print() in the same file didn't do the same for the DHCPv6 options within the HNCP DHCPv6-Data TLV value, which could cause an out-of-bounds read when decoding an invalid packet. Add missing checks to dhcpv6_print(). This fixes a buffer over-read discovered by Bhargava Shastry, SecT/TU Berlin. Add a test using the capture file supplied by the reporter(s). 2017-07-30 01:52:38 +08:00			`Future use: type=16384 (5)`
			`DHCPv6-Data (25)`
			`Unknown (4)`
			`Unknown (4)`
Fix space printing with istr[] Because istr[] is assign to " (invalid)", avoid adding a space before it. Moreover: Avoid also useless '\n' 2018-05-18 15:32:28 +08:00			`SNTP-servers (61956) (invalid)`
Add more nd_print_trunc() calls Update the output of some tests accordingly. 2018-05-06 16:33:07 +08:00			`[\|hncp]`