mirror of
https://github.com/openssl/openssl.git
synced 2024-12-09 05:51:54 +08:00
f7c16d48a9
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) |
||
|---|---|---|
| .. | ||
| cms_add1_signing_cert.pod | ||
| DEFINE_SPARSE_ARRAY_OF.pod | ||
| evp_generic_fetch.pod | ||
| evp_keymgmt_export_to_provider.pod | ||
| evp_keymgmt_freekey.pod | ||
| openssl_ctx_get_data.pod | ||
| ossl_algorithm_do_all.pod | ||
| ossl_init_thread_deregister.pod | ||
| ossl_method_construct.pod | ||
| OSSL_METHOD_STORE.pod | ||
| ossl_namemap_new.pod | ||
| ossl_param_bld_init.pod | ||
| ossl_prov_util_nid_to_name.pod | ||
| ossl_provider_add_conf_module.pod | ||
| ossl_provider_new.pod | ||
| rand_bytes_ex.pod | ||