public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: David Wagner <daw@mozart.cs.berkeley.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Continuing /dev/random problems with 2.4
Date: Sat, 02 Feb 2002 22:02:45 +0100	[thread overview]
Message-ID: <3C5C53F5.1030401@evision-ventures.com> (raw)
In-Reply-To: <20020201031744.A32127@asooo.flowerfire.com> <1012582401.813.1.camel@phantasy> <a3enf3$93p$1@cesium.transmeta.com> <20020201202334.72F921C5@www.pmonta.com> <a3fhh9$u87$1@abraham.cs.berkeley.edu>

David Wagner wrote:

>Peter Monta  wrote:
>
>>Many motherboards have on-board sound.  Why not turn the mic
>>gain all the way up and use the noise---surely there will be
>>a few bits' worth?
>>
>
>That may be reasonable, but beware: there are some potential pitfalls.
>For instance, is there a risk that the audio data you read is strongly
>correlated to 60Hz mains noise in some scenarios?  Also, my understanding
>is that the quality of randomness you get can depend on which sound card
>you have, and moreover that the left and right channels can be strongly
>correlated (audio-entropyd takes the difference between the two).
>I think there are some things you can do, but it seems that one might
>want to be a bit careful here.
>
There is no need to speculate here - just please do aan autocorrelation 
of the signal with grace for example and
laugh at the idea ;-).



  parent reply	other threads:[~2002-02-02 21:03 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  9:17 Continuing /dev/random problems with 2.4 Ken Brownfield
2002-02-01 16:36 ` Andreas Dilger
2002-02-01 17:00   ` Ken Brownfield
2002-02-01 16:53 ` Robert Love
2002-02-01 17:01   ` Ken Brownfield
2002-02-04  9:28     ` Sean Hunter
2002-02-01 18:40   ` H. Peter Anvin
2002-02-01 19:38     ` Ken Brownfield
2002-02-01 19:50       ` Robert Love
2002-02-01 19:52         ` Ken Brownfield
2002-02-01 19:57       ` Andreas Dilger
2002-02-01 20:22         ` Ken Brownfield
2002-02-01 19:43     ` Andreas Dilger
2002-02-01 20:12       ` H. Peter Anvin
2002-02-01 20:28         ` Jeff Garzik
2002-02-02  1:33           ` David Wagner
2002-02-02  8:01             ` Jeff Garzik
2002-02-02  8:54           ` Kai Henningsen
2002-02-02 11:13             ` Andreas Dilger
2002-02-04 22:13         ` Bill Davidsen
2002-02-04 22:37           ` Roland Dreier
2002-02-04 22:45             ` Robert Love
2002-02-05 23:02               ` Bill Davidsen
2002-02-05 23:17                 ` Robert Love
2002-02-06 16:16                   ` Bill Davidsen
2002-02-06 16:31                     ` Need a clew WRT fig2dev Kirk Reiser
2002-02-06 16:42                       ` Adrian Bunk
2002-02-06 20:40                       ` Jeff Garzik
2002-02-09 19:45                     ` Continuing /dev/random problems with 2.4 Nix N. Nix
2002-02-03 12:51       ` Henning P. Schmiedehausen
2002-02-01 20:23     ` Peter Monta
2002-02-01 20:27       ` H. Peter Anvin
2002-02-01 20:36         ` Jeff Garzik
2002-02-01 20:33       ` Jeff Garzik
2002-02-01 20:40         ` H. Peter Anvin
2002-02-01 20:54           ` Jeff Garzik
2002-02-01 20:56         ` Peter Monta
2002-02-01 22:54           ` H. Peter Anvin
2002-02-01 23:27             ` Peter Monta
2002-02-02  1:50               ` H. Peter Anvin
2002-02-02  2:05       ` David Wagner
2002-02-02  3:30         ` Peter Monta
2002-02-02 21:02         ` Martin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-04 21:53 Ishan O. Jayawardena

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=3C5C53F5.1030401@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=daw@mozart.cs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.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