DRBG: make locking api truly private
authorDr. Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
Thu, 15 Feb 2018 09:29:56 +0000 (10:29 +0100)
committerDr. Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
Thu, 15 Feb 2018 11:25:01 +0000 (12:25 +0100)
commit812b15370613da4768d91b9e566fdf5a30c06805
tree918d213ea11ba8623652b4283df0772dbd8c837f
parent4d921bfb8b4161f735e5d3bc19fae264816c9c40
DRBG: make locking api truly private

In PR #5295 it was decided that the locking api should remain private
and used only inside libcrypto. However, the locking functions were added
back to `libcrypto.num` by `mkdef.pl`, because the function prototypes
were still listed in `internal/rand.h`. (This header contains functions
which are internal, but shared between libcrypto and libssl.)

This commit moves the prototypes to `rand_lcl.h` and changes the names
to lowercase, following the convention therein. It also corrects an
outdated documenting comment.

Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5375)
crypto/err/openssl.txt
crypto/rand/drbg_lib.c
crypto/rand/rand_err.c
crypto/rand/rand_lcl.h
crypto/rand/rand_lib.c
include/internal/rand.h
util/libcrypto.num