mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "M Macnair" <mmacnair@gmail.com>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Theodore Tso" <tytso@mit.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: Seeding /dev/random not working
Date: Tue, 29 May 2007 17:31:12 +0200	[thread overview]
Message-ID: <9a8748490705290831x15a552c1q75f858b5509f2f4c@mail.gmail.com> (raw)
In-Reply-To: <de6d2b4f0705290817g2b92f031re29c52ed9f3264a7@mail.gmail.com>

On 29/05/07, M Macnair <mmacnair@gmail.com> wrote:
> On 5/29/07, Pavel Machek <pavel@ucw.cz> wrote:
> > Hi!
> >
> > > > I have two embedded boards (one ARM, one PowerPC), running two
> > > > different versions of 2.6.  They have no hard drives, keyboards or
> > > > mice.  They each have a NIC, but I understand these make no
> > > > contribution to the entropy pool.
> > > >
> > > >     if [ -f $random_seed ]; then
> > > >             cat $random_seed >/dev/urandom  # should seed the pool
> > > >     fi
> > > >     dd if=/dev/urandom of=$random_seed count=1 2>/dev/null # save some
> > > > data from urandom for next boot
> > > >
> > > > I have rebooted my boards many times, and after each boot I read the
> > > > contents of $random_seed.  Whilst it does not happen every time, the
> > > > contents of $random_seed are /often the same/.  To give you a feel:
> > > > rebooted 11 times, got a total of 3 different outputs.
> > >
> > > Ok, so this is telling me a couple of things.  First of all, if you're
> > > only getting three outputs, it means that you don't have any
> > > peripherals feeding entropy into the system from the boot sequence.
> > > Without any hard drives, keyboards or mice, and a NIC whose device
> > > driver hasn't been configured to feed entropy, you're definitely
> > > hosed.
> >
> > Can we get at least time-of-boot from rtc clock to the pool? We really
> > should not be getting identical outputs...
>
> Ah yes that is one thing I forgot to mention - when you turn these
> boards off, you really do turn them off - no battery means no clock.
> They wake up every time in 1970.
>
> I am planning on providing my own entropy to this system by feeding
> /dev/random (which leads to the problem of it not working...).

Depending on how high quality randomness you need, you could just let
your NIC driver provide entropy by changing interrupt handlers to use
SA_SAMPLE_RANDOM.
Sure, getting entropy that way allows an outside attacker to influence
the pool if they can obtain a high degree of control over what data
you recieve and when, but in most realistic scenarios it should be
acceptable (and it's certainly better than no entropy at all).

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2007-05-29 15:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 11:53 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 [this message]
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
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=9a8748490705290831x15a552c1q75f858b5509f2f4c@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmacnair@gmail.com \
    --cc=pavel@ucw.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®