From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
torvalds@osdl.org, netdev@oss.sgi.com,
Chris Wright <chrisw@osdl.org>
Subject: Re: [PATCH] OpenBSD Networking-related randomization port
Date: Fri, 28 Jan 2005 19:36:13 +0100 [thread overview]
Message-ID: <1106937373.3864.10.camel@localhost.localdomain> (raw)
In-Reply-To: <1106935677.7776.29.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
El vie, 28-01-2005 a las 19:07 +0100, Arjan van de Ven escribió:
> On Fri, 2005-01-28 at 18:17 +0100, Lorenzo Hernández García-Hierro
> wrote:
> > Hi,
> >
> > Attached you can find a split up patch ported from grSecurity [1], as
> > Linus commented that he wouldn't get a whole-sale patch, I was working
> > on it and also studying what features of grSecurity can be implemented
> > without a development or maintenance overhead, aka less-invasive
> > implementations.
>
>
> why did you make it a config option? This is the kind of thing that is
> either good or isn't... at which point you can get rid of a lot of, if
> not all the ugly ifdefs the patch adds.
I will remove the ifdef's, I've made it just from the usability POV,
users may want the standard "randomization" schema, dunno.
Anyway, I will remove those ifdef's and make it enabled-by-default.
> Also, why does it need to enhance the random driver this much, the
> random driver already has a facility to provide pseudorandom numbers
> good enough for networking use (eg the PRNG rekeys often enough with
> real entropy that brute forcing it shouldn't be possible).
I will also remove the pool sizes increasing diffs from the patch.
> If you can fix those 2 things the patch will look a lot cleaner and has
> a lot higher chance to be merged.
Sure, many thanks for pointing out that clearly.
It will take a few minutes and then re-send the patch.
Cheers,
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-01-28 18:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1106932637.3778.92.camel@localhost.localdomain>
[not found] ` <20050128174046.GR28047@stusta.de>
[not found] ` <1106934475.3778.98.camel@localhost.localdomain>
2005-01-28 18:18 ` [PATCH] OpenBSD Networking-related randomization port Stephen Hemminger
2005-01-28 18:54 ` Lorenzo Hernández García-Hierro
[not found] ` <20050128100229.5c0e4ea1@dxpl.pdx.osdl.net>
2005-01-28 18:31 ` Lorenzo Hernández García-Hierro
2005-01-28 18:52 ` Stephen Hemminger
2005-01-28 18:58 ` Lorenzo Hernández García-Hierro
2005-01-28 20:34 ` Lorenzo Hernández García-Hierro
2005-01-28 20:45 ` David S. Miller
2005-01-28 21:34 ` Stephen Hemminger
2005-01-28 21:45 ` David S. Miller
2005-01-29 6:59 ` Andi Kleen
2005-01-28 20:47 ` Arjan van de Ven
2005-01-28 22:12 ` Lorenzo Hernández García-Hierro
2005-01-29 8:04 ` Arjan van de Ven
2005-01-29 8:05 ` Arjan van de Ven
2005-01-29 9:15 ` Valdis.Kletnieks
2005-01-31 16:50 ` Adrian Bunk
2005-01-31 17:23 ` Lorenzo Hernández García-Hierro
2005-01-31 20:11 ` Ingo Molnar
2005-01-31 23:27 ` linux
2005-02-12 22:29 ` Andi Kleen
2005-02-12 23:25 ` linux
2005-02-13 0:18 ` Roland Dreier
2005-02-13 1:41 ` linux
2005-02-02 17:17 ` linux
2005-02-02 17:38 ` Lorenzo Hernández García-Hierro
2005-02-03 19:51 ` Stephen Hemminger
2005-02-03 20:14 ` Lennert Buytenhek
2005-01-31 19:42 ` Valdis.Kletnieks
2005-01-31 20:03 ` Lorenzo Hernández García-Hierro
2005-02-01 23:22 ` Matt Mackall
[not found] ` <1106935677.7776.29.camel@laptopd505.fenrus.org>
2005-01-28 18:36 ` Lorenzo Hernández García-Hierro [this message]
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=1106937373.3864.10.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=arjan@infradead.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).