2019-02-25 08:59:02 +08:00
|
|
|
/*
|
|
|
|
* 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
|
|
|
|
* https://www.openssl.org/source/license.html
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef OSSL_INTERNAL_CORE_H
|
|
|
|
# define OSSL_INTERNAL_CORE_H
|
|
|
|
|
|
|
|
/*
|
|
|
|
* namespaces:
|
|
|
|
*
|
|
|
|
* ossl_method_ Core Method API
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* construct an arbitrary method from a dispatch table found by looking
|
|
|
|
* up a match for the < operation_id, name, property > combination.
|
|
|
|
* constructor and destructor are the constructor and destructor for that
|
|
|
|
* arbitrary object.
|
|
|
|
*
|
|
|
|
* These objects are normally cached, unless the provider says not to cache.
|
|
|
|
* However, force_cache can be used to force caching whatever the provider
|
|
|
|
* says (for example, because the application knows better).
|
|
|
|
*/
|
|
|
|
typedef struct ossl_method_construct_method_st {
|
|
|
|
/* Create store */
|
2019-05-01 18:02:43 +08:00
|
|
|
void *(*alloc_tmp_store)(OPENSSL_CTX *ctx);
|
2019-02-25 08:59:02 +08:00
|
|
|
/* Remove a store */
|
|
|
|
void (*dealloc_tmp_store)(void *store);
|
|
|
|
/* Get an already existing method from a store */
|
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 *(*get)(OPENSSL_CTX *libctx, void *store, void *data);
|
2019-02-25 08:59:02 +08:00
|
|
|
/* Store a method in a store */
|
2019-05-05 14:42:21 +08:00
|
|
|
int (*put)(OPENSSL_CTX *libctx, void *store, void *method,
|
2019-08-21 16:08:44 +08:00
|
|
|
const OSSL_PROVIDER *prov, int operation_id, const char *name,
|
|
|
|
const char *propdef, void *data);
|
2019-02-25 08:59:02 +08:00
|
|
|
/* Construct a new method */
|
2019-11-19 16:55:56 +08:00
|
|
|
void *(*construct)(const OSSL_ALGORITHM *algodef, OSSL_PROVIDER *prov,
|
|
|
|
void *data);
|
2019-02-25 08:59:02 +08:00
|
|
|
/* Destruct a method */
|
2019-03-13 18:12:00 +08:00
|
|
|
void (*destruct)(void *method, void *data);
|
2019-02-25 08:59:02 +08:00
|
|
|
} OSSL_METHOD_CONSTRUCT_METHOD;
|
|
|
|
|
|
|
|
void *ossl_method_construct(OPENSSL_CTX *ctx, int operation_id,
|
|
|
|
int force_cache,
|
|
|
|
OSSL_METHOD_CONSTRUCT_METHOD *mcm, void *mcm_data);
|
|
|
|
|
2019-07-11 05:11:27 +08:00
|
|
|
void ossl_algorithm_do_all(OPENSSL_CTX *libctx, int operation_id,
|
|
|
|
OSSL_PROVIDER *provider,
|
|
|
|
void (*fn)(OSSL_PROVIDER *provider,
|
|
|
|
const OSSL_ALGORITHM *algo,
|
|
|
|
int no_store, void *data),
|
|
|
|
void *data);
|
|
|
|
|
2019-02-25 08:59:02 +08:00
|
|
|
#endif
|