they would then need to cause the server to generate a set of headers that provoked the pathological behaviour.
Perhaps I didn't make it clear. It didn't require a specific set of headers. The point of the random key generator script was to demonstrate that it works with any set of headers.
And, how many web servers would still be running that same perl process, with that same random seed 15 minutes later
That 15 minute time wasn't optimised code - it was just proof of concept. I'm sure it could be made much, much faster. It is also parallelisable. And what you do is open a TCP connection to a server process, send one request, keep the connection open, then calculate the seed, then send a second request which DoSes the server. Also, depending on how the perl processes are spawned/forked, they may all share the same hash seed.
In any case, my comment about "unnecessary" was little more than a footnote
But you've spent an awful lot of time since trying to convince anyone who will listen that it isn't a security issue, and you've been shown repeatedly that the assumptions you based this conclusion on were erroneous.

Dave.

In reply to Re^10: Our perl/xs/c app is 30% slower with 64bit 5.24.0, than with 32bit 5.8.9. Why? by dave_the_m
in thread Our perl/xs/c app is 30% slower with 64bit 5.24.0, than with 32bit 5.8.9. Why? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.