From: Juri Haberland <juri@koschikode.com>
To: Mike Dresser <mdresser_l@windsormachine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fragmentation DoS?
Date: Fri, 25 Oct 2002 18:44:03 +0200 [thread overview]
Message-ID: <3DB974D3.5040103@koschikode.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210251235570.21571-100000@router.windsormachine.com>
Mike Dresser wrote:
> Furthermore, if you look at
> http://marc.theaimsgroup.com/?l=cisco-nsp&m=103515530331228&w=2, you'll
> see this person cut/pasted and changed a few words.
>
> And the second link on the securityfocus page is that very lkml post :)
Arghl, I didn't look at the date (I had quite a bit of backlog with
respect to lkml...)
How embarrassing.
Sorry for the noise,
Juri
--
If each of us have one object, and we exchange them,
then each of us still has one object.
If each of us have one idea, and we exchange them,
then each of us now has two ideas.
next prev parent reply other threads:[~2002-10-25 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 19:18 Fragmentation DoS? date
2002-10-19 21:07 ` Matti Aarnio
2002-10-25 15:42 ` Juri Haberland
2002-10-25 16:37 ` Mike Dresser
2002-10-25 16:44 ` Juri Haberland [this message]
2002-10-25 16:47 ` Mike Dresser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DB974D3.5040103@koschikode.com \
--to=juri@koschikode.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdresser_l@windsormachine.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox