ENCODER: use property definitions instead of getting implementation parameters
authorRichard Levitte <levitte@openssl.org>
Wed, 2 Jun 2021 04:37:43 +0000 (06:37 +0200)
committerPauli <pauli@openssl.org>
Sat, 5 Jun 2021 10:30:47 +0000 (20:30 +1000)
commite982e04f5dd12ee2546344b3a26fd0e55f59f5cb
treebecb767d40a55957103c0e365a00c2dc4aeb0018
parent73c02a6201d08afb4ad5055fc3906e1d4504b578
ENCODER: use property definitions instead of getting implementation parameters

The OSSL_ENCODER library used to ask each encoder implementation for
certain data in form of parameters to place them correctly in the
encoder chain, if at all.  These parameters were duplicates of
properties of those same implementations, and therefore unnecessarily
redundant.

Now that we have functionality to query property definition values,
those duplicates are no longer needed, and are therefore not looked at
any more.

Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/15570)
crypto/encode_decode/encoder_lib.c
crypto/encode_decode/encoder_local.h
crypto/encode_decode/encoder_meth.c
doc/man7/provider-encoder.pod