From: andrea.glorioso@binary-only.com
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Are linux network drivers really affected by this?
Date: Mon, 13 Jan 2003 10:54:46 +0100 [thread overview]
Message-ID: <87fzrxwf15.fsf@topo.binary-only.priv> (raw)
In-Reply-To: <200301130658.h0D6w5s26382@Port.imtp.ilyichevsk.odessa.ua> (Denis Vlasenko's message of "Mon, 13 Jan 2003 08:57:47 +0200")
>>>>> "dv" == Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua> writes:
dv> On 10 January 2003 16:53, andrea.glorioso@binary-only.com
dv> wrote:
>> >>>>> "dv" == Denis Vlasenko
>> <vda@port.imtp.ilyichevsk.odessa.ua> >>>>> writes:
>>
dv> Too much work for zero gain
>> `Too much work' refers to coding time or to kernel work?
dv> Coding.
I would have said `kernel work' (although the relative occurrence of
undersized frames is probably low).
dv> IMHO:
dv> Zero padding is secure enough.
Not for fingerprinting, though.
dv> There is no point spending time coding random padding, config
dv> options, etc.
You're probably right.
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-13 9:47 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
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 [this message]
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=87fzrxwf15.fsf@topo.binary-only.priv \
--to=andrea.glorioso@binary-only.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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