summaryrefslogtreecommitdiffstats
path: root/crypto/build.info
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2019-02-19 23:07:57 +0100
committerRichard Levitte <levitte@openssl.org>2019-03-11 20:40:13 +0100
commit3374dc03edda56cbfd2a558fc62b7970eb0b9ad1 (patch)
tree927a72965bf7ac7c9a1ef12c8400578ef7b493a9 /crypto/build.info
parentReplumbing: Add the Provider Object, type OSSL_PROVIDER (diff)
downloadopenssl-3374dc03edda56cbfd2a558fc62b7970eb0b9ad1.tar.xz
openssl-3374dc03edda56cbfd2a558fc62b7970eb0b9ad1.zip
Replumbing: New public API to load or add providers
Adding a provider means creating an internal provier object and adding it to the store. This allows the addition of built in providers, be it in the OpenSSL libraries or in any application. "Loading" a provider is defined broadly. A built in provider is already "loaded" in essence and only needs activating, while a provider in a dynamically loadable module requires actually loading the module itself. In this API, "loading" a provider does both. Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/8287)
Diffstat (limited to 'crypto/build.info')
-rw-r--r--crypto/build.info2
1 files changed, 1 insertions, 1 deletions
diff --git a/crypto/build.info b/crypto/build.info
index fdf0810dbe..0cca6ab7a3 100644
--- a/crypto/build.info
+++ b/crypto/build.info
@@ -17,7 +17,7 @@ SOURCE[../libcrypto]=\
ebcdic.c uid.c o_time.c o_str.c o_dir.c o_fopen.c ctype.c \
threads_pthread.c threads_win.c threads_none.c getenv.c \
o_init.c o_fips.c mem_sec.c init.c context.c sparse_array.c \
- trace.c \
+ trace.c provider.c \
{- $target{cpuid_asm_src} -} {- $target{uplink_aux_src} -}
DEPEND[cversion.o]=buildinf.h