diff options
author | Richard Levitte <levitte@openssl.org> | 2019-11-18 02:31:33 +0100 |
---|---|---|
committer | Richard Levitte <levitte@openssl.org> | 2019-11-29 20:55:16 +0100 |
commit | c48e2d106b8740f817b099310fb084375b743196 (patch) | |
tree | af8076dd40aec5a8af33fd046c60e5480ca71a98 /CHANGES | |
parent | 6ae5543c5f8476f4cae9c00209ef062746bbfd3c (diff) | |
download | openssl-new-c48e2d106b8740f817b099310fb084375b743196.tar.gz |
Add NEWS and CHANGES entries about OSSL_SERIALIZER
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10394)
Diffstat (limited to 'CHANGES')
-rw-r--r-- | CHANGES | 18 |
1 files changed, 18 insertions, 0 deletions
@@ -9,6 +9,24 @@ Changes between 1.1.1 and 3.0.0 [xx XXX xxxx] + *) Introduced a new method type and API, OSSL_SERIALIZER, to + represent generic serializers. An implementation is expected to + be able to serialize an object associated with a given name (such + as an algorithm name for an asymmetric key) into forms given by + implementation properties. + + Serializers are primarily used from inside libcrypto, through + calls to functions like EVP_PKEY_print_private(), + PEM_write_bio_PrivateKey() and similar. + + Serializers are specified in such a way that they can be made to + directly handle the provider side portion of an object, if this + provider side part comes from the same provider as the serializer + itself, but can also be made to handle objects in parametrized + form (as an OSSL_PARAM array of data). This allows a provider to + offer generic serializers as a service for any other provider. + [Richard Levitte] + *) Added a .pragma directive to the syntax of configuration files, to allow varying behavior in a supported and predictable manner. Currently added pragma: |