lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 14 Oct 2014 18:09:54 +0400
From:	"Yurij M. Plotnikov" <>
CC:	"Alexandra N. Kossovsky" <>
Subject: TCP socket receives strange packet

Connected TCP socket receives packet without timestamps option which 
exists in SYN, SYNACK and ACK. It is packet 4 in attached tcpdump output.

tcpdump output description: The host has address (server) 
and the peer host has address (client).

Establishing connection: Timestamps option exists in SYN, SYNACK and ACK 
(packets 1, 2 and 3 in attached file), so accepted socket should receive 
packets only with timestamps option.

Sending packet: the socket receives the packet without timestamps option 
(packet 4 in attached file), i.e. recv() function called on the socket 
receives the data from the packet. The "strange" packet is generated 
using PCAP.

I see this behaviour on 2.6.26 and on 3.14 kernels.

Download attachment "pcap_with_bad_packet" of type "application/octet-stream" (866 bytes)

Powered by blists - more mailing lists