diff options
| author | Jack Lloyd <[email protected]> | 2017-12-03 12:33:42 -0500 |
|---|---|---|
| committer | Jack Lloyd <[email protected]> | 2017-12-04 04:01:06 -0500 |
| commit | 57128566bd57649f7d3a128944e3bde66d415309 (patch) | |
| tree | 4c93a2807a729f977da7f86f76baf536a581c8be /doc/manual/rng.rst | |
| parent | cfd137da35488edb573cb670bedc314671d206f0 (diff) | |
Split up symmetric crypto page into MAC, stream, block and mode pages
Diffstat (limited to 'doc/manual/rng.rst')
| -rw-r--r-- | doc/manual/rng.rst | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/manual/rng.rst b/doc/manual/rng.rst index 11094d832..99cc83914 100644 --- a/doc/manual/rng.rst +++ b/doc/manual/rng.rst @@ -67,7 +67,8 @@ AutoSeeded_RNG AutoSeeded_RNG is type naming a 'best available' userspace PRNG. The exact definition of this has changed over time and may change in the future, fortunately there is no compatability concerns when changing -such an RNG. +any RNG since the only expectation is it produces bits +indistinguishable from random. Note well: like most other classes in Botan, it is not safe to share an instance of ``AutoSeeded_RNG`` among multiple threads without @@ -139,5 +140,7 @@ spawns a new child process himself. If the PID wrapped around, the second child process may get assigned the process ID of it's grandparent and the fork safety can not be ensured. -Therefore, it is strongly recommended to explicitly reseed the -random generator after forking a new process. +Therefore, it is strongly recommended to explicitly reseed any +userspace random generators after forking a new process. If this is +not possible in your application, prefer using the system PRNG +instead. |