1RNGTEST(1)                  General Commands Manual                 RNGTEST(1)
2
3
4

NAME

6       rngtest - Check the randomness of data using FIPS 140-2 tests
7
8

SYNOPSIS

10       rngtest  [-c  n  |  --blockcount=n]  [-b  n  |  --blockstats=n] [-t n |
11       --timedstats=n] [-p | --pipe] [-?] [--help] [-V] [--version]
12
13

DESCRIPTION

15       rngtest works on blocks of 20000 bits at a time, using the  FIPS  140-2
16       (errata  of  2001-10-10) tests to verify the randomness of the block of
17       data.
18
19       It takes input from stdin, and outputs statistics to stderr, optionally
20       echoing  blocks that passed the FIPS tests to stdout (when operating in
21       pipe mode).  Errors are sent to stderr.
22
23       At startup, rngtest will trow away the first 32 bits of data when oper‐
24       ating  in pipe mode.  It will use the next 32 bits of data to bootstrap
25       the FIPS tests (even when not operating in pipe mode).  These bits  are
26       not tested for randomness.
27
28       Statistics are dumped to stderr when the program exits.
29
30

OPTIONS

32       -p, --pipe
33              Enable  pipe mode.  All data blocks that pass the FIPS tests are
34              echoed to stdout, and rngtest operates in silent mode.
35
36       -c n, --blockcount=n (default: 0)
37              Exit after processing n input blocks, if n is not zero.
38
39       -b n, --blockstats=n (default: 0)
40              Dump statistics every n blocks, if n is not zero.
41
42       -t n, --timedstats=n (default: 0)
43              Dump statistics every n seconds, if n is not zero.
44
45       -?, --help
46              Give a short summary of all program options.
47
48       -V, --version
49              Print program version
50
51

STATISTICS

53       rngtest will dump statistics to stderr when it exits, and when told  to
54       by blockstats or timedstats.
55
56       FIPS  140-2  successes  and  FIPS  140-2  failures counts the number of
57       20000-bit blocks either accepted or rejected by the FIPS  140-2  tests.
58       The  other  statistics  show  a breakdown of the FIPS 140-2 failures by
59       FIPS 140-2 test.  See the FIPS  140-2  document  for  more  information
60       (note  that these tests are defined on FIPS 140-1 and FIPS 140-2 errata
61       of 2001-10-10. They were removed in FIPS 140-2 errata of 2002-12-03).
62
63       The speed statistics are taken for every 20000-bit block transferred or
64       processed.
65
66

EXIT STATUS

68       0 if no errors happen, and no blocks fail the FIPS tests.
69
70       1 if no errors happen, but at least one block fails the FIPS tests.
71
72       10 if there are problems with the parameters.
73
74       11 if an input/output error happens.
75
76       12 if an operating system or resource starvation error happens.
77
78

SEE ALSO

80       random(4), rngd(8)
81
82       FIPS PUB 140-2 Security Requirements for Cryptographic Modules, NIST,
83              http://csrc.nist.gov/groups/STM/cmvp/standards.html
84
85

AUTHORS

87       Henrique de Moraes Holschuh <hmh@debian.org>
88
89
90
91
92rng-tools 6.9                     March 2004                        RNGTEST(1)
Impressum