[Cryptech-Commits] [wiki] branch master updated: Clean up one page whose formatting errors were in my face(2)
git at cryptech.is
git at cryptech.is
Thu Mar 17 04:27:44 UTC 2022
This is an automated email from the git hooks/post-receive script.
sra at hactrn.net pushed a commit to branch master
in repository wiki.
The following commit(s) were added to refs/heads/master by this push:
new ac0c73f Clean up one page whose formatting errors were in my face(2)
ac0c73f is described below
Author: Rob Austein <sra at hactrn.net>
AuthorDate: Thu Mar 17 00:27:34 2022 -0400
Clean up one page whose formatting errors were in my face(2)
content/RandomnessTesting.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/content/RandomnessTesting.md b/content/RandomnessTesting.md
index 29001c8..fac6702 100644
@@ -21,6 +21,7 @@ Dieharder is by far the most extensive blackbox test suite. However, it is orig
Generally the best approach to use `dieharder` is to first generate an output file, e.g. `random.out` to run the tests on, so `dieharder` can apply all its individual tests to the same data. For a standard test, at least about 14 GB worth of data are needed; more if one of the tests needing large amounts of data returns a suspect result and `dieharder` re-tries the same test with more data.
The command line options I (bs) personally use are `dieharder -g 201 -f random.out -s 1 -Y 1 -k 2 -a`:
* `-g 201 -f random.out`: Don't use a compiled-in pseudo RNG but the file `random.out` as input.
* `-s 1`: Rewind the input after every test. Without this, successive tests use successive parts of the input file.
* `-Y 1`: Keep testing until a definite (in probabilistic terms:-) test result is obtained.
@@ -28,6 +29,7 @@ The command line options I (bs) personally use are `dieharder -g 201 -f random.o
* `-a`: Run all tests.
Additionally, these may be useful for more targeted testing:
* `-m <n>`: Multiply the `psamples` value by `n`; good for getting even more reliable results, at the expense of the additional data needed.
* `-d <test name/number>`: Perform a specific test.
* `-l`: List all available tests by name and number.
@@ -56,8 +58,10 @@ They generally work on blocks of 20000 bits.
The `rngtest` program reads data from its standard input and by default returns a statistics overview when it reaches EOF. This can be changed with these two options (among others):
* `-c <n>`: Stop running after `n` blocks.
* `-b <n>:` Give intermediate results every `n` blocks.
Use at least one of these when running on a pipe or device...
### Interpretation of Results
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the Commits