netdev
[Top] [All Lists]

Re: [PATCH] OpenBSD Networking-related randomization port

To: Lorenzo Hernández García-Hierro <lorenzo@xxxxxxx>
Subject: Re: [PATCH] OpenBSD Networking-related randomization port
From: Ingo Molnar <mingo@xxxxxxx>
Date: Mon, 31 Jan 2005 21:11:41 +0100
Cc: Adrian Bunk <bunk@xxxxxxxxx>, Valdis.Kletnieks@xxxxxx, Arjan van de Ven <arjan@xxxxxxxxxxxxx>, Stephen Hemminger <shemminger@xxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxx>, netdev@xxxxxxxxxxx, Hank Leininger <hlein@xxxxxxxxxxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, linux@xxxxxxxxxxx
In-reply-to: <1107192218.3754.86.camel@localhost.localdomain>
References: <1106932637.3778.92.camel@localhost.localdomain> <20050128100229.5c0e4ea1@dxpl.pdx.osdl.net> <1106937110.3864.5.camel@localhost.localdomain> <20050128105217.1dc5ef42@dxpl.pdx.osdl.net> <1106944492.3864.30.camel@localhost.localdomain> <1106945266.7776.41.camel@laptopd505.fenrus.org> <200501290915.j0T9FkVY012948@turing-police.cc.vt.edu> <20050131165025.GN18316@stusta.de> <1107192218.3754.86.camel@localhost.localdomain>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
* Lorenzo Hernández García-Hierro <lorenzo@xxxxxxx> wrote:

> > At least the three clause BSD license is GPL compatible.
> 
> Yes, AFAIK :)
> 
> I will try to follow Arjan's recommendations on using his functions
> instead of obsd ones, even if I think it should be alone in the
> current file. Also I will split up the patch.

could you please also react to this feedback:

  http://marc.theaimsgroup.com/?l=linux-kernel&m=110698371131630&w=2

to quote a couple of key points from that very detailed security
analysis:

" I'm not sure how the OpenBSD code is better in any way.  (Notice that
  it uses the same "half_md4_transform" as Linux; you just added another
  copy.) Is there a design note on how the design was chosen? "

that mail also includes a much smaller patch to random.c.

( Obviously the more fundamental questions have to be solved prior
solving code-level problems, patch splitup and patch ordering - often
one ends up having a much smaller patch to work with, by thinking more
about the fundamentals. )

        Ingo

<Prev in Thread] Current Thread [Next in Thread>