From: Jeff Garzik <jgarzik@pobox.com>
To: Yan-Fa Li <yan@intruvert.com>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: FYI: Etherleak
Date: Thu, 9 Jan 2003 21:08:08 -0500 [thread overview]
Message-ID: <20030110020808.GA18605@gtf.org> (raw)
In-Reply-To: <D71BEAC27500D51199DF0002B328BA8D4FBF2B@ivexs1.intruvert.com>
On Thu, Jan 09, 2003 at 05:49:47PM -0800, Yan-Fa Li wrote:
> An interesting report into frame-padding information leakage violations in
> ethernet drivers. The authors use linux drivers in their examples.
>
> http://www.atstake.com/research/advisories/2003/atstake_etherleak_report.pdf
Yes. All of those drivers are for ancient and/or obscure hardware
except three: rtl8139, epic100, and via-rhine.
There are fixes for those (and others) in testing right now, in fact :)
next prev parent reply other threads:[~2003-01-10 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 1:49 FYI: Etherleak Yan-Fa Li
2003-01-10 2:08 ` Jeff Garzik [this message]
2003-01-10 2:12 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 2:14 Yan-Fa Li
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=20030110020808.GA18605@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=yan@intruvert.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;
as well as URLs for NNTP newsgroup(s).