[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070529174614.GG11166@waste.org>
Date: Tue, 29 May 2007 12:46:14 -0500
From: Matt Mackall <mpm@...enic.com>
To: Theodore Tso <tytso@....edu>, M Macnair <mmacnair@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: Seeding /dev/random not working
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);
+
+ return sample.jiffies;
+}
+
+/*
* This function adds entropy to the entropy "pool" by using timing
* delays. It uses the timer_rand_state structure to make an estimate
* of how many bits of entropy this call has added to the pool.
@@ -570,12 +590,7 @@ static struct timer_rand_state *irq_time
*/
static void add_timer_randomness(struct timer_rand_state *state, unsigned num)
{
- struct {
- cycles_t cycles;
- long jiffies;
- unsigned num;
- } sample;
- long delta, delta2, delta3;
+ long timestamp, delta, delta2, delta3;
preempt_disable();
/* if over the trickle threshold, use only 1 in 4096 samples */
@@ -583,10 +598,7 @@ static void add_timer_randomness(struct
(__get_cpu_var(trickle_count)++ & 0xfff))
goto out;
- sample.jiffies = jiffies;
- sample.cycles = get_cycles();
- sample.num = num;
- add_entropy_words(&input_pool, (u32 *)&sample, sizeof(sample)/4);
+ timestamp = __add_timer_randomness();
/*
* Calculate number of bits of randomness we probably added.
@@ -595,8 +607,8 @@ static void add_timer_randomness(struct
*/
if (!state->dont_count_entropy) {
- delta = sample.jiffies - state->last_time;
- state->last_time = sample.jiffies;
+ delta = timestamp - state->last_time;
+ state->last_time = timestamp;
delta2 = delta - state->last_delta;
state->last_delta = delta;
@@ -899,6 +911,7 @@ static int __init rand_initialize(void)
init_std_data(&input_pool);
init_std_data(&blocking_pool);
init_std_data(&nonblocking_pool);
+ __add_timer_randomness();
return 0;
}
module_init(rand_initialize);
@@ -1028,6 +1041,8 @@ random_write(struct file * file, const c
const char __user *p = buffer;
size_t c = count;
+ __add_timer_randomness();
+
while (c > 0) {
bytes = min(c, sizeof(buf));
--
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists