From owner-freebsd-hackers  Fri Sep 27 13:59:06 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA19526
          for hackers-outgoing; Fri, 27 Sep 1996 13:59:06 -0700 (PDT)
Received: from gvr.win.tue.nl (gvr.win.tue.nl [131.155.210.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA19471
          for <hackers@freebsd.org>; Fri, 27 Sep 1996 13:58:57 -0700 (PDT)
Received: by gvr.win.tue.nl (8.6.13/1.53)
    id WAA02273; Fri, 27 Sep 1996 22:57:37 +0200
From: guido@gvr.win.tue.nl (Guido van Rooij)
Message-Id: <199609272057.WAA02273@gvr.win.tue.nl>
Subject: Re: patch against SYN floods (RED impl.)
To: apg@demos.net (Paul Antonov)
Date: Fri, 27 Sep 1996 22:57:37 +0200 (MET DST)
Cc: fenner@parc.xerox.com, apg@demos.net, hackers@freebsd.org
In-Reply-To: <oFyy3JouB0@dream.demos.su> from Paul Antonov at "Sep 28, 96 00:55:24 am"
X-Mailer: ELM [version 2.4ME+ PL17 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Paul Antonov wrote:
> In message <96Sep27.133646pdt.177476@crevenia.parc.xerox.com> Bill
>     Fenner writes:
> 
> >Not only that, but it's relatively dangerous to use information supplied
> >by the attacker as part of your "random" number.  For example, the attacker
> >could vary his initial sequence number by tv_usec / 33 and keep the
> >"random" number constant.
> 
> Yes, I agree that better random function is necessary. My own test flood
> generator uses random seq's - it's too good :) Any ideas?
> 

I thought we had a random generator in the kernel....

-Guido