Details
-
Task
-
Status: Backlog
-
Major - P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
Security
Description
On systems with a /dev/urandom, we defer to the operating system for our source of secure pseudorandom numbers. On other systems, we sort of let the ball drop. We should use a FIPS-140-2 compliant PRNG for SecureRandom on all systems, one way or another.
Attachments
Issue Links
- is related to
-
SERVER-2360 Add a stronger password authentication scheme (replace md5 with sha?)
-
- Closed
-
-
SERVER-7648 Support Use of FIPS 140-2 Compliant Crypto Library
-
- Closed
-
-
SERVER-17422 Improve random number number gen
-
- Closed
-
- related to
-
SERVER-21253 Improve structure and functionality of random number generation classes
-
- Backlog
-
-
SERVER-20919 Use OpenSSL to generate IVs
-
- Closed
-