TCP RST attack (the cause of all that MD5-o-rama)

• Previous message (by thread): TCP RST attack (the cause of all that MD5-o-rama)
• Next message (by thread): TCP RST attack (the cause of all that MD5-o-rama)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 20 Apr 2004 15:40:38 EDT, "Patrick W.Gilmore" said:

> Assuming a well randomized starting sequence number (just give me this 
> one for the moment),

Nope.  I won't give you that one, because that's a big chunk of the
problem:

http://lcamtuf.coredump.cx/newtcp/ (one year later)
http://razor.bindview.com/publish/papers/tcpseq.html  (original paper)

It seems that Cisco has its act mostly together, but a *LOT* of other
vendors don't, even a year after...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20040420/466d8fe7/attachment.sig>

• Previous message (by thread): TCP RST attack (the cause of all that MD5-o-rama)
• Next message (by thread): TCP RST attack (the cause of all that MD5-o-rama)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]