Slashdot Mirror

← Back to Stories (view on slashdot.org)

Graphing Randomness in TCP Initial Sequence Numbers

Posted by michael on from the winning-lottery-numbers-in-there-somewhere dept.

Saint Aardvark writes "This is neat: Graphic visualization of how random TCP Initial Sequence Numbers really are for different OSs. It's a great way of seeing how secure a TCP stack really is. Cisco IOS is great; OS9, OpenVMS and IRIX aren't. Posted to the ever-lovin' BugTraq mailing list." This is a follow-up to the previous report.

2 of 145 comments (clear)

  1. amazing by Phosphor3k · · Score: 5, Funny

    He must be running a server with no tcp stack. heh.

  2. New TCP/IP flags by Tinfoil · · Score: 5, Funny

    I propose a new flag in the standard TCP/IP packet. We shall call this the Slashdot Flag. The general purpose of this flag is to state whether or not the bandwidth limits of the server can handle the requirements a Slashdot posting can impose. If the flag is set false, Slashcode will automatically generate numerous, random, 'this page has been slashdotted' posts requesting a link to a mirror.

    That being said, the page *is* finally loading up so I'm going to go look at some pictures now.

    --

    tinfoilmedia