2008-11-06 02:39:08 +08:00
|
|
|
/*
|
2024-03-20 20:07:54 +08:00
|
|
|
* Copyright 2000-2024 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
|
|
|
*/
|
|
|
|
|
2020-06-21 07:21:19 +08:00
|
|
|
#include <openssl/core_dispatch.h>
|
2020-04-30 12:46:12 +08:00
|
|
|
#include "internal/refcount.h"
|
2019-06-27 17:48:17 +08:00
|
|
|
|
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
|
|
|
|
2021-05-14 11:08:42 +08:00
|
|
|
/*
|
|
|
|
* Opaque ctx returned from a providers digest algorithm implementation
|
|
|
|
* OSSL_FUNC_digest_newctx()
|
|
|
|
*/
|
|
|
|
void *algctx;
|
2019-03-14 00:17:17 +08:00
|
|
|
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 */
|
2022-01-26 12:04:51 +08:00
|
|
|
int iv_len; /* IV length */
|
2015-12-13 23:03:02 +08:00
|
|
|
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
|
|
|
|
2021-05-14 11:08:42 +08:00
|
|
|
/*
|
|
|
|
* Opaque ctx returned from a providers cipher algorithm implementation
|
|
|
|
* OSSL_FUNC_cipher_newctx()
|
|
|
|
*/
|
|
|
|
void *algctx;
|
2019-04-03 22:38:07 +08:00
|
|
|
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 */
|
2021-05-14 11:08:42 +08:00
|
|
|
/*
|
|
|
|
* Opaque ctx returned from a providers MAC algorithm implementation
|
|
|
|
* OSSL_FUNC_mac_newctx()
|
|
|
|
*/
|
|
|
|
void *algctx;
|
2018-10-13 04:27:18 +08:00
|
|
|
} /* 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 */
|
2021-05-14 11:08:42 +08:00
|
|
|
/*
|
|
|
|
* Opaque ctx returned from a providers KDF algorithm implementation
|
|
|
|
* OSSL_FUNC_kdf_newctx()
|
|
|
|
*/
|
|
|
|
void *algctx;
|
2018-06-22 05:16:18 +08:00
|
|
|
} /* EVP_KDF_CTX */ ;
|
|
|
|
|
2020-04-30 12:46:12 +08:00
|
|
|
struct evp_rand_ctx_st {
|
|
|
|
EVP_RAND *meth; /* Method structure */
|
2021-05-14 11:08:42 +08:00
|
|
|
/*
|
|
|
|
* Opaque ctx returned from a providers rand algorithm implementation
|
|
|
|
* OSSL_FUNC_rand_newctx()
|
|
|
|
*/
|
|
|
|
void *algctx;
|
2020-09-16 09:10:01 +08:00
|
|
|
EVP_RAND_CTX *parent; /* Parent EVP_RAND or NULL if none */
|
|
|
|
CRYPTO_REF_COUNT refcnt; /* Context reference count */
|
|
|
|
CRYPTO_RWLOCK *refcnt_lock;
|
2020-04-30 12:46:12 +08:00
|
|
|
} /* EVP_RAND_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;
|
2024-01-11 23:52:35 +08:00
|
|
|
/* NID for the legacy alg if there is one */
|
|
|
|
int legacy_alg;
|
2021-04-16 22:22:03 +08:00
|
|
|
char *type_name;
|
2021-03-16 21:14:43 +08:00
|
|
|
const char *description;
|
2019-07-05 06:31:42 +08:00
|
|
|
OSSL_PROVIDER *prov;
|
|
|
|
CRYPTO_REF_COUNT refcnt;
|
|
|
|
|
Redesign the KEYMGMT libcrypto <-> provider interface - the basics
The KEYMGMT libcrypto <-> provider interface currently makes a few
assumptions:
1. provider side domain parameters and key data isn't mutable. In
other words, as soon as a key has been created in any (loaded,
imported data, ...), it's set in stone.
2. provider side domain parameters can be strictly separated from the
key data.
This does work for the most part, but there are places where that's a
bit too rigid for the functionality that the EVP_PKEY API delivers.
Key data needs to be mutable to allow the flexibility that functions
like EVP_PKEY_copy_parameters promise, as well as to provide the
combinations of data that an EVP_PKEY is generally assumed to be able
to hold:
- domain parameters only
- public key only
- public key + private key
- domain parameters + public key
- domain parameters + public key + private key
To remedy all this, we:
1. let go of the distinction between domain parameters and key
material proper in the libcrypto <-> provider interface.
As a consequence, functions that still need it gain a selection
argument, which is a set of bits that indicate what parts of the
key object are to be considered in a specific call. This allows
a reduction of very similar functions into one.
2. Rework the libcrypto <-> provider interface so provider side key
objects are created and destructed with a separate function, and
get their data filled and extracted in through import and export.
(future work will see other key object constructors and other
functions to fill them with data)
Fixes #10979
squash! Redesign the KEYMGMT libcrypto <-> provider interface - the basics
Remedy 1 needs a rewrite:
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Shane Lontis <shane.lontis@oracle.com>
Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/11006)
2020-02-03 01:56:07 +08:00
|
|
|
/* Constructor(s), destructor, information */
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_keymgmt_new_fn *new;
|
|
|
|
OSSL_FUNC_keymgmt_free_fn *free;
|
|
|
|
OSSL_FUNC_keymgmt_get_params_fn *get_params;
|
|
|
|
OSSL_FUNC_keymgmt_gettable_params_fn *gettable_params;
|
|
|
|
OSSL_FUNC_keymgmt_set_params_fn *set_params;
|
|
|
|
OSSL_FUNC_keymgmt_settable_params_fn *settable_params;
|
2020-01-08 10:44:28 +08:00
|
|
|
|
2019-10-26 19:00:56 +08:00
|
|
|
/* Generation, a complex constructor */
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_keymgmt_gen_init_fn *gen_init;
|
|
|
|
OSSL_FUNC_keymgmt_gen_set_template_fn *gen_set_template;
|
2024-07-24 14:20:14 +08:00
|
|
|
OSSL_FUNC_keymgmt_gen_get_params_fn *gen_get_params;
|
|
|
|
OSSL_FUNC_keymgmt_gen_gettable_params_fn *gen_gettable_params;
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_keymgmt_gen_set_params_fn *gen_set_params;
|
|
|
|
OSSL_FUNC_keymgmt_gen_settable_params_fn *gen_settable_params;
|
|
|
|
OSSL_FUNC_keymgmt_gen_fn *gen;
|
|
|
|
OSSL_FUNC_keymgmt_gen_cleanup_fn *gen_cleanup;
|
2019-10-26 19:00:56 +08:00
|
|
|
|
2020-07-09 04:21:18 +08:00
|
|
|
OSSL_FUNC_keymgmt_load_fn *load;
|
|
|
|
|
Redesign the KEYMGMT libcrypto <-> provider interface - the basics
The KEYMGMT libcrypto <-> provider interface currently makes a few
assumptions:
1. provider side domain parameters and key data isn't mutable. In
other words, as soon as a key has been created in any (loaded,
imported data, ...), it's set in stone.
2. provider side domain parameters can be strictly separated from the
key data.
This does work for the most part, but there are places where that's a
bit too rigid for the functionality that the EVP_PKEY API delivers.
Key data needs to be mutable to allow the flexibility that functions
like EVP_PKEY_copy_parameters promise, as well as to provide the
combinations of data that an EVP_PKEY is generally assumed to be able
to hold:
- domain parameters only
- public key only
- public key + private key
- domain parameters + public key
- domain parameters + public key + private key
To remedy all this, we:
1. let go of the distinction between domain parameters and key
material proper in the libcrypto <-> provider interface.
As a consequence, functions that still need it gain a selection
argument, which is a set of bits that indicate what parts of the
key object are to be considered in a specific call. This allows
a reduction of very similar functions into one.
2. Rework the libcrypto <-> provider interface so provider side key
objects are created and destructed with a separate function, and
get their data filled and extracted in through import and export.
(future work will see other key object constructors and other
functions to fill them with data)
Fixes #10979
squash! Redesign the KEYMGMT libcrypto <-> provider interface - the basics
Remedy 1 needs a rewrite:
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Shane Lontis <shane.lontis@oracle.com>
Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/11006)
2020-02-03 01:56:07 +08:00
|
|
|
/* Key object checking */
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_keymgmt_query_operation_name_fn *query_operation_name;
|
|
|
|
OSSL_FUNC_keymgmt_has_fn *has;
|
|
|
|
OSSL_FUNC_keymgmt_validate_fn *validate;
|
|
|
|
OSSL_FUNC_keymgmt_match_fn *match;
|
Redesign the KEYMGMT libcrypto <-> provider interface - the basics
The KEYMGMT libcrypto <-> provider interface currently makes a few
assumptions:
1. provider side domain parameters and key data isn't mutable. In
other words, as soon as a key has been created in any (loaded,
imported data, ...), it's set in stone.
2. provider side domain parameters can be strictly separated from the
key data.
This does work for the most part, but there are places where that's a
bit too rigid for the functionality that the EVP_PKEY API delivers.
Key data needs to be mutable to allow the flexibility that functions
like EVP_PKEY_copy_parameters promise, as well as to provide the
combinations of data that an EVP_PKEY is generally assumed to be able
to hold:
- domain parameters only
- public key only
- public key + private key
- domain parameters + public key
- domain parameters + public key + private key
To remedy all this, we:
1. let go of the distinction between domain parameters and key
material proper in the libcrypto <-> provider interface.
As a consequence, functions that still need it gain a selection
argument, which is a set of bits that indicate what parts of the
key object are to be considered in a specific call. This allows
a reduction of very similar functions into one.
2. Rework the libcrypto <-> provider interface so provider side key
objects are created and destructed with a separate function, and
get their data filled and extracted in through import and export.
(future work will see other key object constructors and other
functions to fill them with data)
Fixes #10979
squash! Redesign the KEYMGMT libcrypto <-> provider interface - the basics
Remedy 1 needs a rewrite:
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Shane Lontis <shane.lontis@oracle.com>
Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/11006)
2020-02-03 01:56:07 +08:00
|
|
|
|
|
|
|
/* Import and export routines */
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_keymgmt_import_fn *import;
|
|
|
|
OSSL_FUNC_keymgmt_import_types_fn *import_types;
|
2023-02-09 00:26:20 +08:00
|
|
|
OSSL_FUNC_keymgmt_import_types_ex_fn *import_types_ex;
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_keymgmt_export_fn *export;
|
|
|
|
OSSL_FUNC_keymgmt_export_types_fn *export_types;
|
2023-02-09 00:26:20 +08:00
|
|
|
OSSL_FUNC_keymgmt_export_types_ex_fn *export_types_ex;
|
2021-04-08 01:35:13 +08:00
|
|
|
OSSL_FUNC_keymgmt_dup_fn *dup;
|
2019-07-05 06:31:42 +08:00
|
|
|
} /* EVP_KEYMGMT */ ;
|
|
|
|
|
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;
|
2021-04-16 22:22:03 +08:00
|
|
|
char *type_name;
|
2021-03-16 21:14:43 +08:00
|
|
|
const char *description;
|
2019-06-27 17:48:17 +08:00
|
|
|
OSSL_PROVIDER *prov;
|
|
|
|
CRYPTO_REF_COUNT refcnt;
|
|
|
|
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_keyexch_newctx_fn *newctx;
|
|
|
|
OSSL_FUNC_keyexch_init_fn *init;
|
|
|
|
OSSL_FUNC_keyexch_set_peer_fn *set_peer;
|
|
|
|
OSSL_FUNC_keyexch_derive_fn *derive;
|
|
|
|
OSSL_FUNC_keyexch_freectx_fn *freectx;
|
|
|
|
OSSL_FUNC_keyexch_dupctx_fn *dupctx;
|
|
|
|
OSSL_FUNC_keyexch_set_ctx_params_fn *set_ctx_params;
|
|
|
|
OSSL_FUNC_keyexch_settable_ctx_params_fn *settable_ctx_params;
|
|
|
|
OSSL_FUNC_keyexch_get_ctx_params_fn *get_ctx_params;
|
|
|
|
OSSL_FUNC_keyexch_gettable_ctx_params_fn *gettable_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;
|
2021-04-16 22:22:03 +08:00
|
|
|
char *type_name;
|
2021-03-16 21:14:43 +08:00
|
|
|
const char *description;
|
2019-08-30 20:33:10 +08:00
|
|
|
OSSL_PROVIDER *prov;
|
|
|
|
CRYPTO_REF_COUNT refcnt;
|
|
|
|
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_signature_newctx_fn *newctx;
|
|
|
|
OSSL_FUNC_signature_sign_init_fn *sign_init;
|
|
|
|
OSSL_FUNC_signature_sign_fn *sign;
|
2024-01-18 22:27:34 +08:00
|
|
|
OSSL_FUNC_signature_sign_message_init_fn *sign_message_init;
|
|
|
|
OSSL_FUNC_signature_sign_message_update_fn *sign_message_update;
|
|
|
|
OSSL_FUNC_signature_sign_message_final_fn *sign_message_final;
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_signature_verify_init_fn *verify_init;
|
|
|
|
OSSL_FUNC_signature_verify_fn *verify;
|
2024-01-18 22:27:34 +08:00
|
|
|
OSSL_FUNC_signature_verify_message_init_fn *verify_message_init;
|
|
|
|
OSSL_FUNC_signature_verify_message_update_fn *verify_message_update;
|
|
|
|
OSSL_FUNC_signature_verify_message_final_fn *verify_message_final;
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_signature_verify_recover_init_fn *verify_recover_init;
|
|
|
|
OSSL_FUNC_signature_verify_recover_fn *verify_recover;
|
|
|
|
OSSL_FUNC_signature_digest_sign_init_fn *digest_sign_init;
|
|
|
|
OSSL_FUNC_signature_digest_sign_update_fn *digest_sign_update;
|
|
|
|
OSSL_FUNC_signature_digest_sign_final_fn *digest_sign_final;
|
|
|
|
OSSL_FUNC_signature_digest_sign_fn *digest_sign;
|
|
|
|
OSSL_FUNC_signature_digest_verify_init_fn *digest_verify_init;
|
|
|
|
OSSL_FUNC_signature_digest_verify_update_fn *digest_verify_update;
|
|
|
|
OSSL_FUNC_signature_digest_verify_final_fn *digest_verify_final;
|
|
|
|
OSSL_FUNC_signature_digest_verify_fn *digest_verify;
|
|
|
|
OSSL_FUNC_signature_freectx_fn *freectx;
|
|
|
|
OSSL_FUNC_signature_dupctx_fn *dupctx;
|
|
|
|
OSSL_FUNC_signature_get_ctx_params_fn *get_ctx_params;
|
|
|
|
OSSL_FUNC_signature_gettable_ctx_params_fn *gettable_ctx_params;
|
|
|
|
OSSL_FUNC_signature_set_ctx_params_fn *set_ctx_params;
|
|
|
|
OSSL_FUNC_signature_settable_ctx_params_fn *settable_ctx_params;
|
|
|
|
OSSL_FUNC_signature_get_ctx_md_params_fn *get_ctx_md_params;
|
|
|
|
OSSL_FUNC_signature_gettable_ctx_md_params_fn *gettable_ctx_md_params;
|
|
|
|
OSSL_FUNC_signature_set_ctx_md_params_fn *set_ctx_md_params;
|
|
|
|
OSSL_FUNC_signature_settable_ctx_md_params_fn *settable_ctx_md_params;
|
2024-01-18 22:27:34 +08:00
|
|
|
|
|
|
|
/* Signature object checking */
|
|
|
|
OSSL_FUNC_signature_query_key_types_fn *query_key_types;
|
2019-08-30 20:33:10 +08:00
|
|
|
} /* EVP_SIGNATURE */;
|
|
|
|
|
2019-10-01 16:40:57 +08:00
|
|
|
struct evp_asym_cipher_st {
|
|
|
|
int name_id;
|
2021-04-16 22:22:03 +08:00
|
|
|
char *type_name;
|
2021-03-16 21:14:43 +08:00
|
|
|
const char *description;
|
2019-10-01 16:40:57 +08:00
|
|
|
OSSL_PROVIDER *prov;
|
|
|
|
CRYPTO_REF_COUNT refcnt;
|
|
|
|
|
2020-06-21 07:19:16 +08:00
|
|
|
OSSL_FUNC_asym_cipher_newctx_fn *newctx;
|
|
|
|
OSSL_FUNC_asym_cipher_encrypt_init_fn *encrypt_init;
|
|
|
|
OSSL_FUNC_asym_cipher_encrypt_fn *encrypt;
|
|
|
|
OSSL_FUNC_asym_cipher_decrypt_init_fn *decrypt_init;
|
|
|
|
OSSL_FUNC_asym_cipher_decrypt_fn *decrypt;
|
|
|
|
OSSL_FUNC_asym_cipher_freectx_fn *freectx;
|
|
|
|
OSSL_FUNC_asym_cipher_dupctx_fn *dupctx;
|
|
|
|
OSSL_FUNC_asym_cipher_get_ctx_params_fn *get_ctx_params;
|
|
|
|
OSSL_FUNC_asym_cipher_gettable_ctx_params_fn *gettable_ctx_params;
|
|
|
|
OSSL_FUNC_asym_cipher_set_ctx_params_fn *set_ctx_params;
|
|
|
|
OSSL_FUNC_asym_cipher_settable_ctx_params_fn *settable_ctx_params;
|
2019-10-01 16:40:57 +08:00
|
|
|
} /* EVP_ASYM_CIPHER */;
|
|
|
|
|
2020-09-19 16:08:46 +08:00
|
|
|
struct evp_kem_st {
|
|
|
|
int name_id;
|
2021-04-16 22:22:03 +08:00
|
|
|
char *type_name;
|
2021-03-16 21:14:43 +08:00
|
|
|
const char *description;
|
2020-09-19 16:08:46 +08:00
|
|
|
OSSL_PROVIDER *prov;
|
|
|
|
CRYPTO_REF_COUNT refcnt;
|
|
|
|
|
|
|
|
OSSL_FUNC_kem_newctx_fn *newctx;
|
|
|
|
OSSL_FUNC_kem_encapsulate_init_fn *encapsulate_init;
|
|
|
|
OSSL_FUNC_kem_encapsulate_fn *encapsulate;
|
|
|
|
OSSL_FUNC_kem_decapsulate_init_fn *decapsulate_init;
|
|
|
|
OSSL_FUNC_kem_decapsulate_fn *decapsulate;
|
|
|
|
OSSL_FUNC_kem_freectx_fn *freectx;
|
|
|
|
OSSL_FUNC_kem_dupctx_fn *dupctx;
|
|
|
|
OSSL_FUNC_kem_get_ctx_params_fn *get_ctx_params;
|
|
|
|
OSSL_FUNC_kem_gettable_ctx_params_fn *gettable_ctx_params;
|
|
|
|
OSSL_FUNC_kem_set_ctx_params_fn *set_ctx_params;
|
|
|
|
OSSL_FUNC_kem_settable_ctx_params_fn *settable_ctx_params;
|
2022-08-26 09:54:35 +08:00
|
|
|
OSSL_FUNC_kem_auth_encapsulate_init_fn *auth_encapsulate_init;
|
|
|
|
OSSL_FUNC_kem_auth_decapsulate_init_fn *auth_decapsulate_init;
|
2020-09-19 16:08:46 +08:00
|
|
|
} /* EVP_KEM */;
|
|
|
|
|
2009-11-26 06:01:06 +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);
|
2021-02-17 15:56:36 +08:00
|
|
|
int PKCS5_v2_PBKDF2_keyivgen_ex(EVP_CIPHER_CTX *ctx, const char *pass,
|
|
|
|
int passlen, ASN1_TYPE *param,
|
|
|
|
const EVP_CIPHER *c, const EVP_MD *md,
|
|
|
|
int en_de, OSSL_LIB_CTX *libctx, const char *propq);
|
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
|
|
|
|
2021-03-09 12:46:05 +08:00
|
|
|
int ossl_is_partially_overlapping(const void *ptr1, const void *ptr2, int len);
|
2019-02-09 00:01:56 +08:00
|
|
|
|
2019-09-28 06:45:46 +08:00
|
|
|
#include <openssl/types.h>
|
2019-02-09 00:01:56 +08:00
|
|
|
#include <openssl/core.h>
|
|
|
|
|
2020-10-15 17:55:50 +08:00
|
|
|
void *evp_generic_fetch(OSSL_LIB_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,
|
2021-03-16 21:14:43 +08:00
|
|
|
const OSSL_ALGORITHM *algodef,
|
2019-10-31 19:10:01 +08:00
|
|
|
OSSL_PROVIDER *prov),
|
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 *));
|
2021-09-30 15:44:10 +08:00
|
|
|
void *evp_generic_fetch_from_prov(OSSL_PROVIDER *prov, int operation_id,
|
|
|
|
const char *name, const char *properties,
|
|
|
|
void *(*new_method)(int name_id,
|
|
|
|
const OSSL_ALGORITHM *algodef,
|
|
|
|
OSSL_PROVIDER *prov),
|
|
|
|
int (*up_ref_method)(void *),
|
|
|
|
void (*free_method)(void *));
|
2021-06-09 13:50:08 +08:00
|
|
|
void evp_generic_do_all_prefetched(OSSL_LIB_CTX *libctx, int operation_id,
|
|
|
|
void (*user_fn)(void *method, void *arg),
|
|
|
|
void *user_arg);
|
2020-10-15 17:55:50 +08:00
|
|
|
void evp_generic_do_all(OSSL_LIB_CTX *libctx, int operation_id,
|
2019-07-13 12:53:44 +08:00
|
|
|
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,
|
2021-03-16 21:14:43 +08:00
|
|
|
const OSSL_ALGORITHM *algodef,
|
2019-10-31 19:10:01 +08:00
|
|
|
OSSL_PROVIDER *prov),
|
2021-06-09 13:50:08 +08:00
|
|
|
int (*up_ref_method)(void *),
|
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 */
|
2020-10-15 17:55:50 +08:00
|
|
|
EVP_KEYMGMT *evp_keymgmt_fetch_by_number(OSSL_LIB_CTX *ctx, int name_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 *properties);
|
2021-10-01 18:06:52 +08:00
|
|
|
EVP_SIGNATURE *evp_signature_fetch_from_prov(OSSL_PROVIDER *prov,
|
|
|
|
const char *name,
|
|
|
|
const char *properties);
|
|
|
|
EVP_ASYM_CIPHER *evp_asym_cipher_fetch_from_prov(OSSL_PROVIDER *prov,
|
|
|
|
const char *name,
|
|
|
|
const char *properties);
|
|
|
|
EVP_KEYEXCH *evp_keyexch_fetch_from_prov(OSSL_PROVIDER *prov,
|
|
|
|
const char *name,
|
|
|
|
const char *properties);
|
|
|
|
EVP_KEM *evp_kem_fetch_from_prov(OSSL_PROVIDER *prov,
|
|
|
|
const char *name,
|
|
|
|
const char *properties);
|
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
|
|
|
|
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
|
|
|
|
2020-09-07 02:11:34 +08:00
|
|
|
int evp_cipher_get_asn1_aead_params(EVP_CIPHER_CTX *c, ASN1_TYPE *type,
|
|
|
|
evp_cipher_aead_asn1_params *asn1_params);
|
|
|
|
int evp_cipher_set_asn1_aead_params(EVP_CIPHER_CTX *c, ASN1_TYPE *type,
|
|
|
|
evp_cipher_aead_asn1_params *asn1_params);
|
|
|
|
|
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) { \
|
Rename all getters to use get/get0 in name
For functions that exist in 1.1.1 provide a simple aliases via #define.
Fixes #15236
Functions with OSSL_DECODER_, OSSL_ENCODER_, OSSL_STORE_LOADER_,
EVP_KEYEXCH_, EVP_KEM_, EVP_ASYM_CIPHER_, EVP_SIGNATURE_,
EVP_KEYMGMT_, EVP_RAND_, EVP_MAC_, EVP_KDF_, EVP_PKEY_,
EVP_MD_, and EVP_CIPHER_ prefixes are renamed.
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/15405)
2021-05-21 22:58:08 +08:00
|
|
|
size_t pksize = (size_t)EVP_PKEY_get_size(ctx->pkey); \
|
2019-06-27 17:48:17 +08:00
|
|
|
\
|
|
|
|
if (pksize == 0) { \
|
2019-08-17 06:05:08 +08:00
|
|
|
ERR_raise(ERR_LIB_EVP, EVP_R_INVALID_KEY); /*ckerr_ignore*/ \
|
2019-06-27 17:48:17 +08:00
|
|
|
return 0; \
|
|
|
|
} \
|
|
|
|
if (arg == NULL) { \
|
|
|
|
*arglen = pksize; \
|
|
|
|
return 1; \
|
|
|
|
} \
|
|
|
|
if (*arglen < pksize) { \
|
2019-08-17 06:05:08 +08:00
|
|
|
ERR_raise(ERR_LIB_EVP, EVP_R_BUFFER_TOO_SMALL); /*ckerr_ignore*/ \
|
2019-06-27 17:48:17 +08:00
|
|
|
return 0; \
|
|
|
|
} \
|
|
|
|
}
|
2019-09-05 06:13:25 +08:00
|
|
|
|
|
|
|
void evp_pkey_ctx_free_old_ops(EVP_PKEY_CTX *ctx);
|
Add "origin" field to EVP_CIPHER, EVP_MD
Add a "where did this EVP_{CIPHER,MD} come from" flag: global, via fetch,
or via EVP_{CIPHER,MD}_meth_new. Update EVP_{CIPHER,MD}_free to handle all
three origins. The flag is deliberately right before some function pointers,
so that compile-time failures (int/pointer) will occur, as opposed to
taking a bit in the existing "flags" field. The "global variable" flag
is non-zero, so the default case of using OPENSSL_zalloc (for provider
ciphers), will do the right thing. Ref-counting is a no-op for
Make up_ref no-op for global MD and CIPHER objects
Deprecate EVP_MD_CTX_md(). Added EVP_MD_CTX_get0_md() (same semantics as
the deprecated function) and EVP_MD_CTX_get1_md(). Likewise, deprecate
EVP_CIPHER_CTX_cipher() in favor of EVP_CIPHER_CTX_get0_cipher(), and add
EVP_CIPHER_CTX_get1_CIPHER().
Refactor EVP_MD_free() and EVP_MD_meth_free() to call new common
evp_md_free_int() function.
Refactor EVP_CIPHER_free() and EVP_CIPHER_meth_free() to call new common
evp_cipher_free_int() function.
Also change some flags tests to explicit test == or != zero. E.g.,
if (flags & x) --> if ((flags & x) != 0)
if (!(flags & x)) --> if ((flags & x) == 0)
Only done for those lines where "get0_cipher" calls were made.
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/14193)
2021-02-17 06:51:56 +08:00
|
|
|
void evp_cipher_free_int(EVP_CIPHER *md);
|
|
|
|
void evp_md_free_int(EVP_MD *md);
|
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 */
|
2020-01-15 08:04:37 +08:00
|
|
|
int evp_is_a(OSSL_PROVIDER *prov, int number,
|
|
|
|
const char *legacy_name, const char *name);
|
2021-02-20 01:03:43 +08:00
|
|
|
int evp_names_do_all(OSSL_PROVIDER *prov, int number,
|
|
|
|
void (*fn)(const char *name, void *data),
|
|
|
|
void *data);
|
2019-11-18 08:32:36 +08:00
|
|
|
int evp_cipher_cache_constants(EVP_CIPHER *cipher);
|