Attachment 869682 Details for Bug 982660 – A new style configuration file that will work with the latest patch for 2.0.3.

A new style configuration file that will work with the latest patch for 2.0.3.

audio-entropyd (text/plain), 3.20 KB, created by stan on 2014-03-02 19:53:24 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: stan

Created: 2014-03-02 19:53:24 UTC

Size: 3.20 KB

patch

obsolete

># This is the configuration file for audio-entropyd's initscript.
># Each option must be entered on a line by itself as if it was
># being entered on the command line.  The dash must be in the
># first column.
># Anything after a hash (#) mark and blank lines are ignored.
># Command line options override options in this file.
># And this has nothing to do with the options, but you should test the statistical quality of
># audio-entropyd on your setup with cat /dev/random | rngtest -c10000 or another practical number
># The test above takes about 6 hours on my system at 44100 frame rate with entropy-filter=0.
># RG Brown has a good explanation of the relationship of statistics with randomness in his man pages for dieharder.
># I get from 3 to 11 errors on runs.  Statistically, this is expected, but really for good
># cryptographic numbers we don't actually want random numbers, because they include the tails that
># aren't crpytographically secure.  Think patterns like 20 zeros or ones in a row, etc.  So, you'll have to decide
># what seems reasonable.  I think the best way to use this randomness is to make the /dev/urandom device
># more unpredictable.  When audio-entropyd is running, I increase /proc/sys/kernel/random/write_wakeup_threshold
># to 3840 and I lower /proc/sys/kernel/random/urandom_min_reseed_secs to 5,
># providing more entropy and allowing /dev/urandom to take entropy from the pool more often.
>
># Valid options are the following, also see with audio-entropyd -h  or --help
>#
>#--device=plughw:0  #default, you can use hw:0, but your device has to support 32 bit signed output natively
>#--device plughw:0  # original test, you can also leave a space in long options like this does, and short options do
>--device=plughw:0
>#-d plughw:0
>#
>#  I haven't actually compared the filters to see if they extract the *same* entropy.  It seems unlikely.
>#--entropy-filter=10  # original test
>#--entropy-filter=11  # original test, using dc offset to remove bias instead of previous value
>--entropy-filter=0  # new test, default, about the same as 10, the original test
>#--entropy-filter=1  # new test, second difference == 0, more restrictive
>#--entropy-filter=2  # new test, second difference != 0, more restrictive
>#-e 0
>#
># pausing and resuming is the default if the device supports it.  This option causes audio-entropyd
># to open and close the device for each sample it captures, and throws away skip-size samples each time
># before capturing the sample.  This is very inefficient, but ensures that the data gathered is always
># from regular operation.
>#--always_close  
>#-a
>#
>#--do-not-fork  # fork is default
>#-n
>#
>#--sample-rate=22050  # default
>--sample-rate=44100
>#-r 44100
>#
>#--sample-size=11072  # default
>#--sample-size=22144
>#-z 11072
>#
>#--skip-size=11025  # default
>--skip-size=5555
>#-s 11025
>#
>#--internal-test # default is not to do internal testing.  
>#The kernel pool conditions the entropy data it is passed by audio-entropyd regardless.
>#--internal-test
>#-i
>#
>#--store-in-file="/tmp/audio_entropyd_output"  # default is to not store in a file, but to fill the entropy pool
>#-f "/tmp/audio_entropyd_output"
>#
>#--verbose  # default is no messages, more repeats, more messages, max 3 has an effect
>#--verbose
>#--verbose
>#-v
>#-vv
>#-vvv
>#
>#--help
>#-h

Actions: View

Attachments on bug 982660: 815407 | 815408 | 815823 | 815824 | 869266 | 869267 | 869681 | 869682 | 871083 | 871096