2015-01-22 11:40:55 +08:00
|
|
|
/*
|
2019-02-09 00:01:56 +08:00
|
|
|
* Copyright 2000-2019 The OpenSSL Project Authors. All Rights Reserved.
|
2000-05-30 10:21:15 +08:00
|
|
|
*
|
2018-12-06 20:40:06 +08:00
|
|
|
* Licensed under the Apache License 2.0 (the "License"). You may not use
|
2016-05-18 03:38:09 +08:00
|
|
|
* this file except in compliance with the License. You can obtain a copy
|
|
|
|
* in the file LICENSE in the source distribution or at
|
|
|
|
* https://www.openssl.org/source/license.html
|
2000-05-30 10:21:15 +08:00
|
|
|
*/
|
|
|
|
|
2015-11-27 20:35:02 +08:00
|
|
|
/* EVP_MD_CTX related stuff */
|
|
|
|
|
2019-06-27 17:48:17 +08:00
|
|
|
#include <openssl/core_numbers.h>
|
|
|
|
|
2019-07-31 18:34:26 +08:00
|
|
|
#define EVP_CTRL_RET_UNSUPPORTED -1
|
|
|
|
|
|
|
|
|
2015-11-27 20:35:02 +08:00
|
|
|
struct evp_md_ctx_st {
|
2019-03-30 00:28:07 +08:00
|
|
|
const EVP_MD *reqdigest; /* The original requested digest */
|
2015-11-27 20:35:02 +08:00
|
|
|
const EVP_MD *digest;
|
|
|
|
ENGINE *engine; /* functional reference if 'digest' is
|
|
|
|
* ENGINE-provided */
|
|
|
|
unsigned long flags;
|
|
|
|
void *md_data;
|
|
|
|
/* Public key context for sign/verify */
|
|
|
|
EVP_PKEY_CTX *pctx;
|
|
|
|
/* Update function: usually copied from EVP_MD */
|
|
|
|
int (*update) (EVP_MD_CTX *ctx, const void *data, size_t count);
|
2019-03-14 00:17:17 +08:00
|
|
|
|
|
|
|
/* Provider ctx */
|
|
|
|
void *provctx;
|
|
|
|
EVP_MD *fetched_digest;
|
2015-11-27 20:35:02 +08:00
|
|
|
} /* EVP_MD_CTX */ ;
|
|
|
|
|
2015-12-13 23:03:02 +08:00
|
|
|
struct evp_cipher_ctx_st {
|
|
|
|
const EVP_CIPHER *cipher;
|
|
|
|
ENGINE *engine; /* functional reference if 'cipher' is
|
|
|
|
* ENGINE-provided */
|
|
|
|
int encrypt; /* encrypt or decrypt */
|
|
|
|
int buf_len; /* number we have left */
|
|
|
|
unsigned char oiv[EVP_MAX_IV_LENGTH]; /* original iv */
|
|
|
|
unsigned char iv[EVP_MAX_IV_LENGTH]; /* working iv */
|
|
|
|
unsigned char buf[EVP_MAX_BLOCK_LENGTH]; /* saved partial block */
|
|
|
|
int num; /* used by cfb/ofb/ctr mode */
|
|
|
|
/* FIXME: Should this even exist? It appears unused */
|
|
|
|
void *app_data; /* application stuff */
|
|
|
|
int key_len; /* May change for variable length cipher */
|
|
|
|
unsigned long flags; /* Various flags */
|
|
|
|
void *cipher_data; /* per EVP data */
|
|
|
|
int final_used;
|
|
|
|
int block_mask;
|
|
|
|
unsigned char final[EVP_MAX_BLOCK_LENGTH]; /* possible final block */
|
2019-04-03 22:38:07 +08:00
|
|
|
|
|
|
|
/* Provider ctx */
|
|
|
|
void *provctx;
|
|
|
|
EVP_CIPHER *fetched_cipher;
|
2015-12-13 23:03:02 +08:00
|
|
|
} /* EVP_CIPHER_CTX */ ;
|
|
|
|
|
2018-10-13 04:27:18 +08:00
|
|
|
struct evp_mac_ctx_st {
|
2019-05-07 18:39:58 +08:00
|
|
|
EVP_MAC *meth; /* Method structure */
|
2018-10-13 04:27:18 +08:00
|
|
|
void *data; /* Individual method data */
|
|
|
|
} /* EVP_MAC_CTX */;
|
|
|
|
|
2018-06-22 05:16:18 +08:00
|
|
|
struct evp_kdf_ctx_st {
|
2019-08-21 16:54:35 +08:00
|
|
|
EVP_KDF *meth; /* Method structure */
|
|
|
|
void *data; /* Algorithm-specific data */
|
2018-06-22 05:16:18 +08:00
|
|
|
} /* EVP_KDF_CTX */ ;
|
|
|
|
|
2019-07-05 06:31:42 +08:00
|
|
|
struct evp_keymgmt_st {
|
|
|
|
int id; /* libcrypto internal */
|
|
|
|
|
In provider implemented methods, save the name number, not the name string
Multiple names per implementation is already supported in the namemap,
but hasn't been used yet. However, as soon as we have multiple names,
we will get an issue with what name should be saved in the method.
The solution is to not save the name itself, but rather the number
it's associated with. This number is supposed to be unique for each
set of names, and we assume that algorithm names are globally unique,
i.e. there can be no name overlap between different algorithm types.
Incidently, it was also found that the 'get' function used by
ossl_construct_method() doesn't need all the parameters it was given;
most of what it needs, it can now get through the data structure given
by the caller of ossl_construct_method(). As a consequence,
ossl_construct_method() itself doesn't need all the parameters it was
given either.
There are some added internal functions that are expected to disappear
as soon as legacy code is removed, such as evp_first_name() and
ossl_namemap_num2name().
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9897)
2019-09-14 22:22:19 +08:00
|
|
|
int name_id;
|
2019-07-05 06:31:42 +08:00
|
|
|
OSSL_PROVIDER *prov;
|
|
|
|
CRYPTO_REF_COUNT refcnt;
|
|
|
|
CRYPTO_RWLOCK *lock;
|
|
|
|
|
|
|
|
/* Domain parameter routines */
|
|
|
|
OSSL_OP_keymgmt_importdomparams_fn *importdomparams;
|
|
|
|
OSSL_OP_keymgmt_gendomparams_fn *gendomparams;
|
|
|
|
OSSL_OP_keymgmt_freedomparams_fn *freedomparams;
|
|
|
|
OSSL_OP_keymgmt_exportdomparams_fn *exportdomparams;
|
|
|
|
OSSL_OP_keymgmt_importdomparam_types_fn *importdomparam_types;
|
|
|
|
OSSL_OP_keymgmt_exportdomparam_types_fn *exportdomparam_types;
|
|
|
|
|
|
|
|
/* Key routines */
|
|
|
|
OSSL_OP_keymgmt_importkey_fn *importkey;
|
|
|
|
OSSL_OP_keymgmt_genkey_fn *genkey;
|
|
|
|
OSSL_OP_keymgmt_loadkey_fn *loadkey;
|
|
|
|
OSSL_OP_keymgmt_freekey_fn *freekey;
|
|
|
|
OSSL_OP_keymgmt_exportkey_fn *exportkey;
|
|
|
|
OSSL_OP_keymgmt_importkey_types_fn *importkey_types;
|
|
|
|
OSSL_OP_keymgmt_exportkey_types_fn *exportkey_types;
|
|
|
|
} /* EVP_KEYMGMT */ ;
|
|
|
|
|
2019-08-30 20:33:10 +08:00
|
|
|
struct keymgmt_data_st {
|
|
|
|
OPENSSL_CTX *ctx;
|
|
|
|
const char *properties;
|
|
|
|
};
|
|
|
|
|
2019-06-27 17:48:17 +08:00
|
|
|
struct evp_keyexch_st {
|
In provider implemented methods, save the name number, not the name string
Multiple names per implementation is already supported in the namemap,
but hasn't been used yet. However, as soon as we have multiple names,
we will get an issue with what name should be saved in the method.
The solution is to not save the name itself, but rather the number
it's associated with. This number is supposed to be unique for each
set of names, and we assume that algorithm names are globally unique,
i.e. there can be no name overlap between different algorithm types.
Incidently, it was also found that the 'get' function used by
ossl_construct_method() doesn't need all the parameters it was given;
most of what it needs, it can now get through the data structure given
by the caller of ossl_construct_method(). As a consequence,
ossl_construct_method() itself doesn't need all the parameters it was
given either.
There are some added internal functions that are expected to disappear
as soon as legacy code is removed, such as evp_first_name() and
ossl_namemap_num2name().
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9897)
2019-09-14 22:22:19 +08:00
|
|
|
int name_id;
|
2019-06-27 17:48:17 +08:00
|
|
|
OSSL_PROVIDER *prov;
|
|
|
|
CRYPTO_REF_COUNT refcnt;
|
|
|
|
CRYPTO_RWLOCK *lock;
|
|
|
|
|
2019-07-07 16:56:46 +08:00
|
|
|
EVP_KEYMGMT *keymgmt;
|
|
|
|
|
2019-06-27 17:48:17 +08:00
|
|
|
OSSL_OP_keyexch_newctx_fn *newctx;
|
|
|
|
OSSL_OP_keyexch_init_fn *init;
|
|
|
|
OSSL_OP_keyexch_set_peer_fn *set_peer;
|
|
|
|
OSSL_OP_keyexch_derive_fn *derive;
|
|
|
|
OSSL_OP_keyexch_freectx_fn *freectx;
|
|
|
|
OSSL_OP_keyexch_dupctx_fn *dupctx;
|
2019-09-04 19:46:02 +08:00
|
|
|
OSSL_OP_keyexch_set_ctx_params_fn *set_ctx_params;
|
|
|
|
OSSL_OP_keyexch_settable_ctx_params_fn *settable_ctx_params;
|
2019-06-27 17:48:17 +08:00
|
|
|
} /* EVP_KEYEXCH */;
|
|
|
|
|
2019-08-30 20:33:10 +08:00
|
|
|
struct evp_signature_st {
|
In provider implemented methods, save the name number, not the name string
Multiple names per implementation is already supported in the namemap,
but hasn't been used yet. However, as soon as we have multiple names,
we will get an issue with what name should be saved in the method.
The solution is to not save the name itself, but rather the number
it's associated with. This number is supposed to be unique for each
set of names, and we assume that algorithm names are globally unique,
i.e. there can be no name overlap between different algorithm types.
Incidently, it was also found that the 'get' function used by
ossl_construct_method() doesn't need all the parameters it was given;
most of what it needs, it can now get through the data structure given
by the caller of ossl_construct_method(). As a consequence,
ossl_construct_method() itself doesn't need all the parameters it was
given either.
There are some added internal functions that are expected to disappear
as soon as legacy code is removed, such as evp_first_name() and
ossl_namemap_num2name().
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9897)
2019-09-14 22:22:19 +08:00
|
|
|
int name_id;
|
2019-08-30 20:33:10 +08:00
|
|
|
OSSL_PROVIDER *prov;
|
|
|
|
CRYPTO_REF_COUNT refcnt;
|
|
|
|
CRYPTO_RWLOCK *lock;
|
|
|
|
|
|
|
|
EVP_KEYMGMT *keymgmt;
|
|
|
|
|
|
|
|
OSSL_OP_signature_newctx_fn *newctx;
|
|
|
|
OSSL_OP_signature_sign_init_fn *sign_init;
|
|
|
|
OSSL_OP_signature_sign_fn *sign;
|
2019-09-02 23:48:26 +08:00
|
|
|
OSSL_OP_signature_verify_init_fn *verify_init;
|
|
|
|
OSSL_OP_signature_verify_fn *verify;
|
|
|
|
OSSL_OP_signature_verify_recover_init_fn *verify_recover_init;
|
|
|
|
OSSL_OP_signature_verify_recover_fn *verify_recover;
|
2019-08-30 20:33:10 +08:00
|
|
|
OSSL_OP_signature_freectx_fn *freectx;
|
|
|
|
OSSL_OP_signature_dupctx_fn *dupctx;
|
2019-09-04 19:46:02 +08:00
|
|
|
OSSL_OP_signature_get_ctx_params_fn *get_ctx_params;
|
|
|
|
OSSL_OP_signature_gettable_ctx_params_fn *gettable_ctx_params;
|
|
|
|
OSSL_OP_signature_set_ctx_params_fn *set_ctx_params;
|
|
|
|
OSSL_OP_signature_settable_ctx_params_fn *settable_ctx_params;
|
2019-08-30 20:33:10 +08:00
|
|
|
} /* EVP_SIGNATURE */;
|
|
|
|
|
2015-01-22 11:40:55 +08:00
|
|
|
int PKCS5_v2_PBKDF2_keyivgen(EVP_CIPHER_CTX *ctx, const char *pass,
|
|
|
|
int passlen, ASN1_TYPE *param,
|
|
|
|
const EVP_CIPHER *c, const EVP_MD *md,
|
|
|
|
int en_de);
|
2015-12-11 23:07:48 +08:00
|
|
|
|
|
|
|
struct evp_Encode_Ctx_st {
|
|
|
|
/* number saved in a partial encode/decode */
|
|
|
|
int num;
|
|
|
|
/*
|
|
|
|
* The length is either the output line length (in input bytes) or the
|
|
|
|
* shortest input line length that is ok. Once decoding begins, the
|
|
|
|
* length is adjusted up each time a longer line is decoded
|
|
|
|
*/
|
|
|
|
int length;
|
|
|
|
/* data to encode */
|
|
|
|
unsigned char enc_data[80];
|
|
|
|
/* number read on current line */
|
|
|
|
int line_num;
|
2018-04-09 22:06:50 +08:00
|
|
|
unsigned int flags;
|
2015-12-11 23:07:48 +08:00
|
|
|
};
|
2016-01-06 10:54:18 +08:00
|
|
|
|
|
|
|
typedef struct evp_pbe_st EVP_PBE_CTL;
|
|
|
|
DEFINE_STACK_OF(EVP_PBE_CTL)
|
2017-01-24 20:57:34 +08:00
|
|
|
|
|
|
|
int is_partially_overlapping(const void *ptr1, const void *ptr2, int len);
|
2019-02-09 00:01:56 +08:00
|
|
|
|
|
|
|
#include <openssl/ossl_typ.h>
|
|
|
|
#include <openssl/core.h>
|
|
|
|
|
|
|
|
void *evp_generic_fetch(OPENSSL_CTX *ctx, int operation_id,
|
In provider implemented methods, save the name number, not the name string
Multiple names per implementation is already supported in the namemap,
but hasn't been used yet. However, as soon as we have multiple names,
we will get an issue with what name should be saved in the method.
The solution is to not save the name itself, but rather the number
it's associated with. This number is supposed to be unique for each
set of names, and we assume that algorithm names are globally unique,
i.e. there can be no name overlap between different algorithm types.
Incidently, it was also found that the 'get' function used by
ossl_construct_method() doesn't need all the parameters it was given;
most of what it needs, it can now get through the data structure given
by the caller of ossl_construct_method(). As a consequence,
ossl_construct_method() itself doesn't need all the parameters it was
given either.
There are some added internal functions that are expected to disappear
as soon as legacy code is removed, such as evp_first_name() and
ossl_namemap_num2name().
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9897)
2019-09-14 22:22:19 +08:00
|
|
|
const char *name, const char *properties,
|
|
|
|
void *(*new_method)(int name_id,
|
2019-07-11 04:22:16 +08:00
|
|
|
const OSSL_DISPATCH *fns,
|
2019-08-23 20:03:28 +08:00
|
|
|
OSSL_PROVIDER *prov,
|
|
|
|
void *method_data),
|
|
|
|
void *method_data,
|
2019-07-02 20:57:36 +08:00
|
|
|
int (*up_ref_method)(void *),
|
2019-05-08 20:00:31 +08:00
|
|
|
void (*free_method)(void *));
|
In provider implemented methods, save the name number, not the name string
Multiple names per implementation is already supported in the namemap,
but hasn't been used yet. However, as soon as we have multiple names,
we will get an issue with what name should be saved in the method.
The solution is to not save the name itself, but rather the number
it's associated with. This number is supposed to be unique for each
set of names, and we assume that algorithm names are globally unique,
i.e. there can be no name overlap between different algorithm types.
Incidently, it was also found that the 'get' function used by
ossl_construct_method() doesn't need all the parameters it was given;
most of what it needs, it can now get through the data structure given
by the caller of ossl_construct_method(). As a consequence,
ossl_construct_method() itself doesn't need all the parameters it was
given either.
There are some added internal functions that are expected to disappear
as soon as legacy code is removed, such as evp_first_name() and
ossl_namemap_num2name().
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9897)
2019-09-14 22:22:19 +08:00
|
|
|
void *evp_generic_fetch_by_number(OPENSSL_CTX *ctx, int operation_id,
|
|
|
|
int name_id, const char *properties,
|
|
|
|
void *(*new_method)(int name_id,
|
|
|
|
const OSSL_DISPATCH *fns,
|
|
|
|
OSSL_PROVIDER *prov,
|
|
|
|
void *method_data),
|
|
|
|
void *method_data,
|
|
|
|
int (*up_ref_method)(void *),
|
|
|
|
void (*free_method)(void *));
|
2019-07-13 12:53:44 +08:00
|
|
|
void evp_generic_do_all(OPENSSL_CTX *libctx, int operation_id,
|
|
|
|
void (*user_fn)(void *method, void *arg),
|
|
|
|
void *user_arg,
|
In provider implemented methods, save the name number, not the name string
Multiple names per implementation is already supported in the namemap,
but hasn't been used yet. However, as soon as we have multiple names,
we will get an issue with what name should be saved in the method.
The solution is to not save the name itself, but rather the number
it's associated with. This number is supposed to be unique for each
set of names, and we assume that algorithm names are globally unique,
i.e. there can be no name overlap between different algorithm types.
Incidently, it was also found that the 'get' function used by
ossl_construct_method() doesn't need all the parameters it was given;
most of what it needs, it can now get through the data structure given
by the caller of ossl_construct_method(). As a consequence,
ossl_construct_method() itself doesn't need all the parameters it was
given either.
There are some added internal functions that are expected to disappear
as soon as legacy code is removed, such as evp_first_name() and
ossl_namemap_num2name().
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9897)
2019-09-14 22:22:19 +08:00
|
|
|
void *(*new_method)(int name_id,
|
2019-07-13 12:53:44 +08:00
|
|
|
const OSSL_DISPATCH *fns,
|
2019-08-23 20:03:28 +08:00
|
|
|
OSSL_PROVIDER *prov,
|
|
|
|
void *method_data),
|
|
|
|
void *method_data,
|
2019-07-13 12:53:44 +08:00
|
|
|
void (*free_method)(void *));
|
2019-07-09 13:32:16 +08:00
|
|
|
|
In provider implemented methods, save the name number, not the name string
Multiple names per implementation is already supported in the namemap,
but hasn't been used yet. However, as soon as we have multiple names,
we will get an issue with what name should be saved in the method.
The solution is to not save the name itself, but rather the number
it's associated with. This number is supposed to be unique for each
set of names, and we assume that algorithm names are globally unique,
i.e. there can be no name overlap between different algorithm types.
Incidently, it was also found that the 'get' function used by
ossl_construct_method() doesn't need all the parameters it was given;
most of what it needs, it can now get through the data structure given
by the caller of ossl_construct_method(). As a consequence,
ossl_construct_method() itself doesn't need all the parameters it was
given either.
There are some added internal functions that are expected to disappear
as soon as legacy code is removed, such as evp_first_name() and
ossl_namemap_num2name().
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9897)
2019-09-14 22:22:19 +08:00
|
|
|
/* Internal fetchers for method types that are to be combined with others */
|
|
|
|
EVP_KEYMGMT *evp_keymgmt_fetch_by_number(OPENSSL_CTX *ctx, int name_id,
|
|
|
|
const char *properties);
|
|
|
|
|
2019-09-03 23:47:13 +08:00
|
|
|
/* Internal structure constructors for fetched methods */
|
|
|
|
EVP_MD *evp_md_new(void);
|
2019-09-04 00:11:49 +08:00
|
|
|
EVP_CIPHER *evp_cipher_new(void);
|
2019-09-03 23:47:13 +08:00
|
|
|
|
2019-07-09 13:32:16 +08:00
|
|
|
/* Helper functions to avoid duplicating code */
|
|
|
|
|
|
|
|
/*
|
2019-07-16 07:46:14 +08:00
|
|
|
* These methods implement different ways to pass a params array to the
|
2019-07-09 13:32:16 +08:00
|
|
|
* provider. They will return one of these values:
|
|
|
|
*
|
|
|
|
* -2 if the method doesn't come from a provider
|
|
|
|
* (evp_do_param will return this to the called)
|
|
|
|
* -1 if the provider doesn't offer the desired function
|
|
|
|
* (evp_do_param will raise an error and return 0)
|
|
|
|
* or the return value from the desired function
|
|
|
|
* (evp_do_param will return it to the caller)
|
|
|
|
*/
|
2019-07-16 07:46:14 +08:00
|
|
|
int evp_do_ciph_getparams(const EVP_CIPHER *ciph, OSSL_PARAM params[]);
|
|
|
|
int evp_do_ciph_ctx_getparams(const EVP_CIPHER *ciph, void *provctx,
|
2019-07-09 13:32:16 +08:00
|
|
|
OSSL_PARAM params[]);
|
2019-07-16 07:46:14 +08:00
|
|
|
int evp_do_ciph_ctx_setparams(const EVP_CIPHER *ciph, void *provctx,
|
2019-07-09 13:32:16 +08:00
|
|
|
OSSL_PARAM params[]);
|
2019-07-16 12:03:12 +08:00
|
|
|
int evp_do_md_getparams(const EVP_MD *md, OSSL_PARAM params[]);
|
|
|
|
int evp_do_md_ctx_getparams(const EVP_MD *md, void *provctx,
|
|
|
|
OSSL_PARAM params[]);
|
|
|
|
int evp_do_md_ctx_setparams(const EVP_MD *md, void *provctx,
|
|
|
|
OSSL_PARAM params[]);
|
2019-06-27 17:48:17 +08:00
|
|
|
|
|
|
|
OSSL_PARAM *evp_pkey_to_param(EVP_PKEY *pkey, size_t *sz);
|
|
|
|
|
|
|
|
#define M_check_autoarg(ctx, arg, arglen, err) \
|
|
|
|
if (ctx->pmeth->flags & EVP_PKEY_FLAG_AUTOARGLEN) { \
|
|
|
|
size_t pksize = (size_t)EVP_PKEY_size(ctx->pkey); \
|
|
|
|
\
|
|
|
|
if (pksize == 0) { \
|
|
|
|
EVPerr(err, EVP_R_INVALID_KEY); /*ckerr_ignore*/ \
|
|
|
|
return 0; \
|
|
|
|
} \
|
|
|
|
if (arg == NULL) { \
|
|
|
|
*arglen = pksize; \
|
|
|
|
return 1; \
|
|
|
|
} \
|
|
|
|
if (*arglen < pksize) { \
|
|
|
|
EVPerr(err, EVP_R_BUFFER_TOO_SMALL); /*ckerr_ignore*/ \
|
|
|
|
return 0; \
|
|
|
|
} \
|
|
|
|
}
|
2019-09-05 06:13:25 +08:00
|
|
|
|
|
|
|
void evp_pkey_ctx_free_old_ops(EVP_PKEY_CTX *ctx);
|
In provider implemented methods, save the name number, not the name string
Multiple names per implementation is already supported in the namemap,
but hasn't been used yet. However, as soon as we have multiple names,
we will get an issue with what name should be saved in the method.
The solution is to not save the name itself, but rather the number
it's associated with. This number is supposed to be unique for each
set of names, and we assume that algorithm names are globally unique,
i.e. there can be no name overlap between different algorithm types.
Incidently, it was also found that the 'get' function used by
ossl_construct_method() doesn't need all the parameters it was given;
most of what it needs, it can now get through the data structure given
by the caller of ossl_construct_method(). As a consequence,
ossl_construct_method() itself doesn't need all the parameters it was
given either.
There are some added internal functions that are expected to disappear
as soon as legacy code is removed, such as evp_first_name() and
ossl_namemap_num2name().
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9897)
2019-09-14 22:22:19 +08:00
|
|
|
|
|
|
|
/* OSSL_PROVIDER * is only used to get the library context */
|
|
|
|
const char *evp_first_name(OSSL_PROVIDER *prov, int name_id);
|
2019-09-14 22:35:08 +08:00
|
|
|
int evp_is_a(OSSL_PROVIDER *prov, int number, const char *name);
|