Lines Matching +full:composite +full:- +full:in

5 ----------------
11 - `EVP_SIGNATURE`
13 Public API - Add variants of `EVP_PKEY_CTX` functionality
14 ---------------------------------------------------------
22 when the fetched algorithm permits it (for example, RSA-SHA256).
27 hash "SHA256" to get the "RSA-SHA256" functionality.  For an `EVP_SIGNATURE`
34 pre-computed digest of a message (under the condition that proper flags
40 This design proposes an extension to also allow full (not pre-hashed)
41 messages to be passed, in a streaming style through an *update* and a
50 …]: the term "primitive" is borrowed from [PKCS#1](https://www.rfc-editor.org/rfc/rfc8017#section-5)
60 New public API - API Reference
61 ------------------------------
78                                  const unsigned char *in,
108                                    const unsigned char *in,
129 -----------------------------
131 Because it's not immediately obvious from a composite algorithm name what
132 key type ("RSA", "EC", ...) it requires / supports, at least in code, allowing
133 the use of an explicitly fetched implementation of a composite algorithm
137 For non-composite operation algorithms (like "RSA"), this is not necessary,
150 to be a pre-hashed digest or the original message, must be passed on to the
151 provider.  Because we already distinguish that with function names in the
152 public API, we use the same mapping in the provider interface.
164                     (void *ctx, const unsigned char *in, size_t inlen))
174                     (void *ctx, const unsigned char *in, size_t inlen))
183 -------------------
188 for pre-hashed digest operations).  To find out if the `EVP_PKEY` key type
192 -   Check if the fetched operation name matches the key type (keymgmt name)
193     of the `EVP_PKEY` that's involved in the operation.  For example, this
197 -   Check if the fetched algorithm name matches the name returned by the