lists.openwall.net   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  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:	Tue, 20 Mar 2007 10:56:46 -0500
From:	"Robert Liang" <liangrob@...il.com>
To:	netdev@...r.kernel.org
Subject: example of tcp dsack undo

Hi,

While designing some testing examples for the undo mechanisms, I found that
undo_dsack is only used when the state is Disorder. However, I assume that
dsack happens when there are retransmissions, which means Recovery or Loss.

I can think of an example of receiving dsack following a successful
recovery. But
the dsack ACKs old data and can not bring the state into Disorder.
Can anybody give me an example when *valid* dsack is received while in Disorder
state.


Thank you!

rl
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ