From: andrea.glorioso@binary-only.com
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Are linux network drivers really affected by this?
Date: Fri, 10 Jan 2003 09:08:55 +0100 [thread overview]
Message-ID: <87iswx4eaw.fsf@topo.binary-only.priv> (raw)
In-Reply-To: <1042116723.2556.3.camel@station3> (Nils Petter Vaskinn's message of "09 Jan 2003 13:52:03 +0100")
>>>>> "npv" == Nils Petter Vaskinn <nils.petter.vaskinn@itsopen.net> writes:
npv> http://www.kb.cert.org/vuls/id/412115
npv> Summary: Some network drivers don't pad ethernet packets with
npv> nulls, they are filled with "garbage" often from previously
npv> sent packets. Linux is mentioned as vulnerable.
The paper presented by Olaf Arkin (amongst other) points to some parts
of the linux code where this "vulnerability" exists. I think Alan Cox
is working on some patches for his tree. I wonder whether it's better
to null-pad ethernet packets or to fill them with random values
(possibly an overkill, but more resiliant against fingerprinting).
bye,
andrea
--
Andrea Glorioso andrea.glorioso@binary-only.com
Binary Only http://www.binary-only.com/
Via A. Zanolini, 7/b Tel: +39-348.921.43.79
40126 Bologna Fax: +39-051-930.31.133
next prev parent reply other threads:[~2003-01-10 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 12:52 Are linux network drivers really affected by this? Nils Petter Vaskinn
2003-01-10 8:08 ` andrea.glorioso [this message]
2003-01-10 11:46 ` Alan Cox
2003-01-10 11:12 ` andrea.glorioso
2003-01-10 12:11 ` Denis Vlasenko
2003-01-10 14:53 ` andrea.glorioso
2003-01-13 6:57 ` Denis Vlasenko
2003-01-13 9:54 ` andrea.glorioso
2003-01-14 1:19 ` Miles Bader
2003-01-18 14:09 ` Folkert van Heusden
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=87iswx4eaw.fsf@topo.binary-only.priv \
--to=andrea.glorioso@binary-only.com \
--cc=linux-kernel@vger.kernel.org \
/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