/share/man/man4/rndtest.4

https://bitbucket.org/freebsd/freebsd-head/ · Forth · 72 lines · 72 code · 0 blank · 0 comment · 2 complexity · c4980bbe54416da9ce9840049b38603e MD5 · raw file 

    

  1. .\"-
    2. 

  2. .\" Copyright (c) 2003 Sam Leffler, Errno Consulting
    3. 

  3. .\" All rights reserved.
    4. 

  4. .\"
    5. 

  5. .\" Redistribution and use in source and binary forms, with or without
    6. 

  6. .\" modification, are permitted provided that the following conditions
    7. 

  7. .\" are met:
    8. 

  8. .\" 1. Redistributions of source code must retain the above copyright
    9. 

  9. .\"    notice, this list of conditions and the following disclaimer.
    10. 

  10. .\" 2. Redistributions in binary form must reproduce the above copyright
    11. 

  11. .\"    notice, this list of conditions and the following disclaimer in the
    12. 

  12. .\"    documentation and/or other materials provided with the distribution.
    13. 

  13. .\"
    14. 

  14. .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
    15. 

  15. .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
    16. 

  16. .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
    17. 

  17. .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
    18. 

  18. .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
    19. 

  19. .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
    20. 

  20. .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
    21. 

  21. .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
    22. 

  22. .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
    23. 

  23. .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
    24. 

  24. .\" SUCH DAMAGE.
    25. 

  25. .\"
    26. 

  26. .\" $FreeBSD$
    27. 

  27. .\"
    28. 

  28. .Dd March 11, 2003
    29. 

  29. .Dt RNDTEST 4
    30. 

  30. .Os
    31. 

  31. .Sh NAME
    32. 

  32. .Nm rndtest
    33. 

  33. .Nd FIPS 140-2 random number generator test monitor
    34. 

  34. .Sh SYNOPSIS
    35. 

  35. .Cd "device rndtest"
    36. 

  36. .Sh DESCRIPTION
    37. 

  37. The
    38. 

  38. .Nm
    39. 

  39. driver
    40. 

  40. .Dq "hooks up"
    41. 

  41. to hardware crypto devices to monitor the
    42. 

  42. entropy data passed to the
    43. 

  43. .Xr random 4
    44. 

  44. subsystem.
    45. 

  45. This data is periodically tested for FIPS 140-2 compliance and
    46. 

  46. statistics are collected.
    47. 

  47. If the harvested entropy fails any of the FIPS test suite, then
    48. 

  48. it is discarded and testing is continuously applied until
    49. 

  49. .Dq "good data"
    50. 

  50. is received from the device.
    51. 

  51. Failures are optionally reported on the console.
    52. 

  52. .Sh SEE ALSO
    53. 

  53. .Xr crypto 4 ,
    54. 

  54. .Xr hifn 4 ,
    55. 

  55. .Xr random 4 ,
    56. 

  56. .Xr safe 4 ,
    57. 

  57. .Xr ubsec 4 ,
    58. 

  58. .Xr crypto 9
    59. 

  59. .Sh HISTORY
    60. 

  60. The idea for this and the original code came from
    61. 

  61. .An "Jason L. Wright" .
    62. 

  62. The
    63. 

  63. .Nm
    64. 

  64. device driver first appeared in
    65. 

  65. .Fx 5.0 .
    66. 

  66. .Sh BUGS
    67. 

  67. Crypto device drivers must be compiled specially to make use of this driver;
    68. 

  68. this should not be necessary.
    69. 

  69. This feature might better be integrated into the
    70. 

  70. .Xr random 4
    71. 

  71. subsystem where it can be applied to devices that claim to supply
    72. 

  72. .Dq "pure entropy" .
    73.