Lines Matching full:algorithm

97 ### 2.4 Algorithm Query and Invocation
101 …er querying suitable algorithms. See the corresponding headers for each algorithm for more details.
127     - `operaId`: Algorithm category ID (see "crypt_eal_implprovider.h").
128     - `algId`: Algorithm ID (see "crypt_eal_implprovider.h").
131 …t `NULL`, it retrieves the `provCtx` from the provider manager context where the algorithm resides.
156 …on during handshakes. Each `group` must support either a `kex` or `kem` algorithm. Through this me…
163 - `CRYPT_PARAM_CAP_TLS_GROUP_ALG_ID`: Type `BSL_PARAM_TYPE_INT32`, algorithm ID for the group, pass…
166 …_CAP_TLS_GROUP_IS_KEM`: Type `BSL_PARAM_TYPE_BOOL`, indicates whether the group is a KEM algorithm.
177 …ignature algorithm` supported by a provider can be declared through the callback passed to `CRYPT_…
181 …M_CAP_TLS_SIGNALG_KEY_TYPE`: Type `BSL_PARAM_TYPE_INT32`, key type used by the signature algorithm.
184 …AM_CAP_TLS_SIGNALG_PARA_ID`: Type `BSL_PARAM_TYPE_INT32`, parameter ID for the signature algorithm.
185 …ARA_OID`: Type `BSL_PARAM_TYPE_OCTETS_PTR`, OID corresponding to the signature algorithm parameter.
186 …LS_SIGNALG_PARA_NAME`: Type `BSL_PARAM_TYPE_OCTETS_PTR`, name of the signature algorithm parameter.
190 - `CRYPT_PARAM_CAP_TLS_SIGNALG_SIGN_ID`: Type `BSL_PARAM_TYPE_INT32`, signature algorithm ID.
191 - `CRYPT_PARAM_CAP_TLS_SIGNALG_MD_ID`: Type `BSL_PARAM_TYPE_INT32`, digest algorithm ID.
192 …P_TLS_SIGNALG_MD_OID`: Type `BSL_PARAM_TYPE_OCTETS_PTR`, OID corresponding to the digest algorithm.
193 …YPT_PARAM_CAP_TLS_SIGNALG_MD_NAME`: Type `BSL_PARAM_TYPE_OCTETS_PTR`, name of the digest algorithm.
194 …NALG_SEC_BITS`: Type `BSL_PARAM_TYPE_INT32`, security strength provided by the signature algorithm.
195 …PE_UINT32`, certificate chain version bitmap supported by the signature algorithm. See `*_VERSION_…
196 …RAM_TYPE_UINT32`, certificate version bitmap supported by the signature algorithm. See `*_VERSION_…
211 …- Currently, OpenHiTLS's built-in algorithm library is loaded into a globally initialized library …
245 …for algorithms matching the algorithm ID. If the search string is not `NULL`, it further selects t…
246 …algorithm attributes are composed of a `name` and a `value`, separated by `=`. Multiple attributes…
262     // Query with a NULL attribute string, searching by algorithm ID
274     // For actual use, it is recommended to use EAL layer wrapping interfaces for each algorithm,
275     // which automatically locate and initialize the algorithm.
303 …- `capFuncs`: [in] Algorithm array pointer provided by the management framework, allowing users to…
309 …This array is used to pass the three types of algorithm arrays provided by the provider. **The alg…
310 …- **Algorithm Query Function**: Used to retrieve the algorithm array provided by the provider base…
314             - `operaId`: [in] Algorithm category ID.
315 …inter to the array of all algorithms under the category. The array ends when the algorithm ID is 0.
399 - **Algorithm query function example**:
448 /* Using the SM3 algorithm */
454 // Using the built-in HITLS algorithm library:
461 // Searching and initializing with a matching algorithm library in a third-party provider:
495 // After initialization, a series of algorithm operations can be performed: