RNGTEST(1)                                            General Commands Manual                                            RNGTEST(1)

NAME
       rngtest - Check the randomness of data using FIPS 140-2 tests

SYNOPSIS
       rngtest [-c n | --blockcount=n] [-b n | --blockstats=n] [-t n | --timedstats=n] [-p | --pipe] [-?] [--help] [-V] [--version]

DESCRIPTION
       rngtest  works on blocks of 20000 bits at a time, using the FIPS 140-2 (errata of 2001-10-10) tests to verify the randomness
       of the block of data.

       It takes input from stdin, and outputs statistics to stderr, optionally echoing blocks that passed the FIPS tests to  stdout
       (when operating in pipe mode).  Errors are sent to stderr.

       At  startup, rngtest will throw away the first 32 bits of data when operating in pipe mode.  It will use the next 32 bits of
       data to bootstrap the FIPS tests (even when not operating in pipe mode).  These bits are not tested for randomness.

       Statistics are dumped to stderr when the program exits.

OPTIONS
       -p, --pipe
              Enable pipe mode.  All data blocks that pass the FIPS tests are echoed to stdout,  and  rngtest  operates  in  silent
              mode.

       -c n, --blockcount=n (default: 0)
              Exit after processing n input blocks, if n is not zero.

       -b n, --blockstats=n (default: 0)
              Dump statistics every n blocks, if n is not zero.

       -t n, --timedstats=n (default: 0)
              Dump statistics every n secods, if n is not zero.

       -?, --help
              Give a short summary of all program options.

       -V, --version
              Print program version

STATISTICS
       rngtest will dump statistics to stderr when it exits, and when told to by blockstats or timedstats.

       FIPS  140-2  successes and FIPS 140-2 failures counts the number of 20000-bit blocks either accepted or rejected by the FIPS
       140-2 tests.  The other statistics show a breakdown of the FIPS 140-2 failures by FIPS 140-2 test.  See the FIPS 140-2 docu‐
       ment  for  more  information (note that these tests are defined on FIPS 140-1 and FIPS 140-2 errata of 2001-10-10. They were
       removed in FIPS 140-2 errata of 2002-12-03).

       The speed statistics are taken for every 20000-bit block trasferred or processed.

EXIT STATUS
       0 if no errors happen, and no blocks fail the FIPS tests.

       1 if no errors happen, but at least one block fails the FIPS tests.

       10 if there are problems with the parameters.

       11 if an input/output error happens.

       12 if an operating system or resource starvation error happens.

SEE ALSO
       random(4), rngd(8)

       FIPS PUB 140-2 Security Requirements for Cryptographic Modules, NIST,
              http://csrc.nist.gov/cryptval/140-2.htm

AUTHORS
       Henrique de Moraes Holschuh <hmh@debian.org>

rng-tools 2-unofficial-mt.14                                 March 2004                                                  RNGTEST(1)

Usage: rngtest [OPTION...]
Check the randomness of data using FIPS 140-2 RNG tests.

  -b, --blockstats=n         Dump statistics every n blocks (default: 0)
  -c, --blockcount=n         Exit after processing n blocks (default: 0)
  -p, --pipe                 Enable pipe mode: work silently, and echo to
                             stdout all good blocks
  -t, --timedstats=n         Dump statistics every n secods (default: 0)
  -?, --help                 Give this help list
      --usage                Give a short usage message
  -V, --version              Print program version

Mandatory or optional arguments to long options are also mandatory or optional
for any corresponding short options.

FIPS tests operate on 20000-bit blocks.  Data is read from stdin.  Statistics
and messages are sent to stderr.

If no errors happen nor any blocks fail the FIPS tests, the program will return
exit status 0.  If any blocks fail the tests, the exit status will be 1.

Report bugs to rng-tools@packages.debian.org.