Allow RNG code to be compiled out about libsrtp HOT 3 CLOSED

When configuring libsrtp with the --enable-openssl option, the RNG in librstp is removed. It's replaced with a shim layer that utilizes the OpenSSL RNG. OpenSSL has several RNG implementations within it, including SP800-90A.

from libsrtp.

339b61d begins the effort to remove the RNG. As discussed on another thread, libsrtp shouldn't be used as a general purpose crypto library. The public API for 2.0 will be limited to SRTP features, while the underlying crypto API will no longer be public. This includes the RNG, which is outdated and not current with standards such as SP800-90.

There is one remaining challenge to completely remove the RNG from libsrtp. The problem is the crypto kernel code uses the RNG to derive test data for the cipher invertibility test, which is part of the cipher self test logic. We may have to retain some of the RNG logic in the library for the self test routine. But it will not be exposed through a public header file.

from libsrtp.

fb83841 resolves this issue. The RNG is no longer available in 2.0.

from libsrtp.