From: Eric Dumazet <dada1@cosmosbay.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Theodore Tso <tytso@mit.edu>, M Macnair <mmacnair@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Seeding /dev/random not working
Date: Tue, 29 May 2007 21:23:31 +0200 [thread overview]
Message-ID: <465C7DB3.104@cosmosbay.com> (raw)
In-Reply-To: <20070529174614.GG11166@waste.org>
Matt Mackall a écrit :
> On Tue, May 29, 2007 at 09:15:01AM -0400, Theodore Tso wrote:
>> Another thing which I noticed is that when Matt Mackall took over
>> maintainership of /dev/random, he apparently took out one of the
>> safeguards I had, which was that before, when entropy was extracted
>> from the pool the time stamp when it was extracted was mixed back into
>> the pool. The theory was that an external attacker might not know
>> when a program might be calling /dev/random, so mixing in the time of
>> that entropy was extracted wouldn't hurt, and might help. I'll submit
>> a patch to add that support back in, which will help you a little.
>
> It's still there, and in the same place, it just looks different:
>
> static void add_timer_randomness(struct timer_rand_state *state,
> unsigned num)
> {
> ...
> sample.jiffies = jiffies;
> sample.cycles = get_cycles();
> sample.num = num;
> add_entropy_words(&input_pool, (u32 *)&sample,
> sizeof(sample)/4);
>
> Trouble is the write(2) interface calls add_entropy_words directly, as
> does the pool initialization function.
>
> We might as well mix jiffies and cycles in at init time in a manner
> similar to the above. Something like this (untested):
>
> Index: l/drivers/char/random.c
> ===================================================================
> --- l.orig/drivers/char/random.c 2007-05-29 12:45:00.000000000 -0500
> +++ l/drivers/char/random.c 2007-05-29 12:44:02.000000000 -0500
> @@ -559,6 +559,26 @@ static struct timer_rand_state input_tim
> static struct timer_rand_state *irq_timer_state[NR_IRQS];
>
> /*
> + * Mix a sample of the current time into the pool with no entropy
> + * accounting
> + */
> +static long __add_timer_randomness(void)
> +{
> + struct {
> + cycles_t cycles;
> + long jiffies;
> + unsigned num;
> + } sample;
> +
> + sample.jiffies = jiffies;
> + sample.cycles = get_cycles();
> + sample.num = num;
> + add_entropy_words(&input_pool, (u32 *)&sample, sizeof(sample)/4);
Well, you need to pass 'num' argument I guess.
But... How is this supposed to work on 64 bits arches ?
Because of alignment, 'struct sample' will include a 4 bytes filler after
'unsigned num', and sizeof(sample) will include this (null) filler in entropy
pool.
Shouldn't we use __attribute__((packed)) on 'struct sample' definition ?
next prev parent reply other threads:[~2007-05-29 19:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 11:53 Seeding /dev/random not working M Macnair
2007-05-29 13:15 ` Theodore Tso
2007-05-29 13:38 ` M Macnair
2007-05-29 14:14 ` Pavel Machek
2007-05-29 15:17 ` M Macnair
2007-05-29 15:31 ` Jesper Juhl
2007-05-29 16:30 ` Theodore Tso
2007-05-29 20:06 ` Folkert van Heusden
2007-05-29 17:46 ` Matt Mackall
2007-05-29 18:00 ` Matt Mackall
2007-05-29 19:23 ` Eric Dumazet [this message]
2007-05-29 19:35 ` Matt Mackall
2007-05-29 16:58 ` Andi Kleen
2007-05-29 16:44 ` M Macnair
2007-05-29 20:23 ` Matt Mackall
2007-05-29 22:08 ` Andi Kleen
2007-05-29 21:44 ` Matt Mackall
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=465C7DB3.104@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmacnair@gmail.com \
--cc=mpm@selenic.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.