aboutsummaryrefslogtreecommitdiff
path: root/CHANGES.md
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2021-09-07 11:28:12 +0200
committerRichard Levitte <levitte@openssl.org>2021-09-07 13:14:40 +0200
commit4c4ab4d7efdf8c9b49c9838742a0fcd7321d88ff (patch)
tree556d88cdfea809c5e1f492243f26e7b96f99f021 /CHANGES.md
parent76b45e5ac8e133ee672639125267bda6f0b5a4b0 (diff)
downloadopenssl-4c4ab4d7efdf8c9b49c9838742a0fcd7321d88ff.zip
openssl-4c4ab4d7efdf8c9b49c9838742a0fcd7321d88ff.tar.gz
openssl-4c4ab4d7efdf8c9b49c9838742a0fcd7321d88ff.tar.bz2
Mention the concept of providers in NEWS.md and CHANGES.md
Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/16528)
Diffstat (limited to 'CHANGES.md')
-rw-r--r--CHANGES.md17
1 files changed, 17 insertions, 0 deletions
diff --git a/CHANGES.md b/CHANGES.md
index bc6d951..5578b0e 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -1389,6 +1389,23 @@ breaking changes, and mappings for the large list of deprecated functions.
*Raja Ashok*
+ * Added a new concept for OpenSSL plugability: providers. This
+ functionality is designed to replace the ENGINE API and ENGINE
+ implementations, and to be much more dynamic, allowing provider
+ authors to introduce new algorithms among other things, as long as
+ there's an API that supports the algorithm type.
+
+ With this concept comes a new core API for interaction between
+ libcrypto and provider implementations. Public libcrypto functions
+ that want to use providers do so through this core API.
+
+ The main documentation for this core API is found in
+ doc/man7/provider.pod, doc/man7/provider-base.pod, and they in turn
+ refer to other manuals describing the API specific for supported
+ algorithm types (also called operations).
+
+ *The OpenSSL team*
+
OpenSSL 1.1.1
-------------