* TCP sequence number security fixes for stable
@ 2013-01-08 17:13 Ben Hutchings
0 siblings, 0 replies; only message in thread
From: Ben Hutchings @ 2013-01-08 17:13 UTC (permalink / raw)
To: David Miller; +Cc: Eric Dumazet, John Dykstra, netdev
Please consider these for your stable update queue:
282f23c6ee343 tcp: implement RFC 5961 3.2
0c24604b68fc7 tcp: implement RFC 5961 4.2
e371589917011 tcp: refine SYN handling in tcp_validate_incoming
bd090dfc634dd tcp: tcp_replace_ts_recent() should not be called from tcp_validate_incoming()
354e4aa391ed5 tcp: RFC 5961 5.2 Blind Data Injection Attack Mitigation
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-01-08 17:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-08 17:13 TCP sequence number security fixes for stable Ben Hutchings
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox