public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: andrea.glorioso@binary-only.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Are linux network drivers really affected by this?
Date: Fri, 10 Jan 2003 12:12:17 +0100	[thread overview]
Message-ID: <8765sx2r8u.fsf@topo.binary-only.priv> (raw)
In-Reply-To: <1042199207.28469.49.camel@irongate.swansea.linux.org.uk> (Alan Cox's message of "10 Jan 2003 11:46:48 +0000")

>>>>> "ac" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

    ac> Most of  them will pad with zero.  We have a couple of drivers
    ac> that already pad with something along  the lines of "NetBSD is
    ac> a cool OS too.."

Let's talk about subliminal messages, then. :)

How sensible would it be to have a runtime or  compile time option for
choosing between zero padding and  random values padding?  I think the
variable length of the  padding could cause some performance problems,
but I'm no kernel hacker nor cryptography expert.

    ac> The -ac tree should have the problem fixed for all the drivers
    ac> I know have the problem or may do.

Great.

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

  reply	other threads:[~2003-01-10 11:04 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 [this message]
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=8765sx2r8u.fsf@topo.binary-only.priv \
    --to=andrea.glorioso@binary-only.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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