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
|
|
|
=pod
|
|
|
|
|
|
|
|
=head1 NAME
|
|
|
|
|
|
|
|
evp_keymgmt_newdata, evp_keymgmt_freedata,
|
|
|
|
evp_keymgmt_get_params, evp_keymgmt_gettable_params,
|
|
|
|
evp_keymgmt_has, evp_keymgmt_validate,
|
|
|
|
evp_keymgmt_import, evp_keymgmt_import_types,
|
|
|
|
evp_keymgmt_export, evp_keymgmt_export_types
|
|
|
|
- internal KEYMGMT interface functions
|
|
|
|
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
|
|
|
|
#include "crypto/evp.h"
|
|
|
|
|
|
|
|
void *evp_keymgmt_newdata(const EVP_KEYMGMT *keymgmt);
|
|
|
|
void evp_keymgmt_freedata(const EVP_KEYMGMT *keymgmt, void *keyddata);
|
|
|
|
int evp_keymgmt_get_params(const EVP_KEYMGMT *keymgmt,
|
|
|
|
void *keydata, OSSL_PARAM params[]);
|
|
|
|
const OSSL_PARAM *evp_keymgmt_gettable_params(const EVP_KEYMGMT *keymgmt);
|
2020-02-09 03:20:47 +08:00
|
|
|
|
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
|
|
|
int evp_keymgmt_has(const EVP_KEYMGMT *keymgmt, void *keyddata, int selection);
|
|
|
|
int evp_keymgmt_validate(const EVP_KEYMGMT *keymgmt, void *keydata,
|
|
|
|
int selection);
|
2020-02-09 03:20:47 +08:00
|
|
|
|
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
|
|
|
int evp_keymgmt_import(const EVP_KEYMGMT *keymgmt, void *keydata,
|
|
|
|
int selection, const OSSL_PARAM params[]);
|
|
|
|
const OSSL_PARAM *evp_keymgmt_import_types(const EVP_KEYMGMT *keymgmt,
|
|
|
|
int selection);
|
|
|
|
int evp_keymgmt_export(const EVP_KEYMGMT *keymgmt, void *keydata,
|
|
|
|
int selection, OSSL_CALLBACK *param_cb, void *cbarg);
|
|
|
|
const OSSL_PARAM *evp_keymgmt_export_types(const EVP_KEYMGMT *keymgmt,
|
|
|
|
int selection);
|
|
|
|
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
|
|
|
|
All these functions are helpers to call the provider's corresponding
|
|
|
|
function. They all have in common that they take a B<EVP_KEYMGMT> as
|
|
|
|
first argument, which they also retrieve a provider context from when
|
|
|
|
needed. The rest of the arguments are simply passed on to the
|
|
|
|
function they wrap around.
|
|
|
|
|
|
|
|
evp_keymgmt_newdata() calls the method's new() function.
|
|
|
|
|
|
|
|
evp_keymgmt_freedata() calls the method's free() function.
|
|
|
|
|
|
|
|
(the name evp_keymgmt_freedata() was chosen to avoid a clash with
|
|
|
|
EVP_KEYMGMT_free() on case insensitive systems, the name
|
|
|
|
evp_keymgmt_newdata() was chosen for consistency)
|
|
|
|
|
|
|
|
evp_keymgmt_get_params() calls the method's get_params() function.
|
|
|
|
|
|
|
|
evp_keymgmt_gettable_params() calls the method's gettable_params()
|
|
|
|
function.
|
|
|
|
|
|
|
|
evp_keymgmt_has() calls the method's has() function.
|
|
|
|
|
|
|
|
evp_keymgmt_validate() calls the method's validate() function.
|
|
|
|
|
|
|
|
evp_keymgmt_import() calls the method's import() function.
|
|
|
|
|
|
|
|
evp_keymgmt_import_types() calls the method's import_types() function.
|
|
|
|
|
|
|
|
evp_keymgmt_export() calls the method's export() function.
|
|
|
|
|
|
|
|
evp_keymgmt_export_types() calls the method's export_types() function.
|
|
|
|
|
|
|
|
=head1 RETURN VALUES
|
|
|
|
|
|
|
|
evp_keymgmt_newdata() returns a pointer to a provider side key object,
|
|
|
|
or NULL on error.
|
|
|
|
|
|
|
|
evp_keymgmt_gettable_params(), evp_keymgmt_import_types(), and
|
|
|
|
evp_keymgmt_export_types() return parameter descriptor for importing
|
|
|
|
and exporting key data, or NULL if there are no such descriptors.
|
|
|
|
|
|
|
|
All other functions return 1 on success and 0 on error.
|
|
|
|
|
|
|
|
=head1 HISTORY
|
|
|
|
|
|
|
|
The functions described here were all added in OpenSSL 3.0.
|
|
|
|
|
|
|
|
=head1 COPYRIGHT
|
|
|
|
|
|
|
|
Copyright 2019 The OpenSSL Project Authors. All Rights Reserved.
|
|
|
|
|
|
|
|
Licensed under the Apache License 2.0 (the "License"). You may not use
|
|
|
|
this file except in compliance with the License. You can obtain a copy
|
|
|
|
in the file LICENSE in the source distribution or at
|
|
|
|
L<https://www.openssl.org/source/license.html>.
|
|
|
|
|
|
|
|
=cut
|