diff options
| author | Scott <scott@paragonie.com> | 2016-03-09 07:28:59 -0500 |
|---|---|---|
| committer | Scott <scott@paragonie.com> | 2016-03-09 07:28:59 -0500 |
| commit | abe5c4aa4fac4362345224982ea672f033bb7d59 (patch) | |
| tree | 13d10ef180541b51ee989e2e699005ed626f20e5 | |
| parent | 15220d8be718c3e12249c98767c00b4f92a387f0 (diff) | |
| download | random_compat-abe5c4aa4fac4362345224982ea672f033bb7d59.zip random_compat-abe5c4aa4fac4362345224982ea672f033bb7d59.tar.gz random_compat-abe5c4aa4fac4362345224982ea672f033bb7d59.tar.bz2 | |
Update ERRATA.md
| -rw-r--r-- | ERRATA.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -25,8 +25,8 @@ the remaining implementations. The reason is simple: `mcrypt_create_iv()` is part of PHP's `ext/mcrypt` code, and is not part `libmcrypt`. It actually does the right thing: - * On Unix-based operating systems, it reads from `/dev/urandom`, which is the - sane and correct thing to do. + * On Unix-based operating systems, it reads from `/dev/urandom`, which unlike `/dev/random` + is the sane and correct thing to do. * On Windows, it reads from `CryptGenRandom`, which is an exclusively Windows way to get random bytes. |