Lines Matching refs:signature

5 provider-signature - The signature library E<lt>-E<gt> provider functions
88 The signature (OSSL_OP_SIGNATURE) operation enables providers to implement
89 signature algorithms and make them available to applications via the API
147 A signature algorithm implementation may not implement all of these functions.
150 set of "signature" functions, i.e. at least one of:
175 A signature algorithm must also implement some mechanism for generating,
182 structure for holding context information during a signature operation.
183 A pointer to this context will be passed back in a number of the other signature
190 OSSL_FUNC_signature_freectx() is passed a pointer to the provider side signature
194 OSSL_FUNC_signature_dupctx() should duplicate the provider side signature context in
200 signature context in the I<ctx> parameter, and a pointer to a provider key object
209 A previously initialised signature context is passed in the I<ctx>
213 Unless I<sig> is NULL, the signature should be written to the location pointed
215 The length of the signature should be written to I<*siglen>.
216 If I<sig> is NULL then the maximum length of the signature should be written to
221 OSSL_FUNC_signature_verify_init() initialises a context for verifying a signature given
222 a provider side signature context in the I<ctx> parameter, and a pointer to a
231 A previously initialised signature context is passed in the I<ctx> parameter.
232 The data that the signature covers is pointed to be the I<tbs> parameter which
234 The signature is pointed to by the I<sig> parameter which is I<siglen> bytes
240 signed data given a provider side signature context in the I<ctx> parameter, and
249 A previously initialised signature context is passed in the I<ctx> parameter.
250 The signature is pointed to by the I<sig> parameter which is I<siglen> bytes
261 provider side signature context in the I<ctx> parameter, and a pointer to a
273 signature context is passed in the I<ctx> parameter. This function may be called
276 OSSL_FUNC_signature_digest_sign_final() finalises a signature operation previously
280 signature context is passed in the I<ctx> parameter. Unless I<sig> is NULL, the
281 signature should be written to the location pointed to by the I<sig> parameter
282 and it should not exceed I<sigsize> bytes in length. The length of the signature
284 the signature should be written to I<*siglen>.
288 initialised signature context is passed in the I<ctx> parameter. The data to be
290 the signature should be written to the location pointed to by the I<sig>
292 signature should be written to I<*siglen>. If I<sig> is NULL then the maximum
293 length of the signature should be written to I<*siglen>.
317 verification context is passed in the I<ctx> parameter. The signature to be
323 verified is in I<tbs> which should be I<tbslen> bytes long. The signature to be
331 OSSL_FUNC_signature_get_ctx_params() gets signature parameters associated with the
332 given provider side signature context I<ctx> and stored them in I<params>.
335 OSSL_FUNC_signature_set_ctx_params() sets the signature parameters associated with the
336 given provider side signature context I<ctx> to I<params>.
340 Common parameters currently recognised by built-in signature algorithms are as
348 signature functions. It is required in order to calculate the "algorithm-id".
358 signature functions.
364 signature algorithm and digest algorithm for the signature operation.
369 calculated signature is invalid.
371 signature operation succeeds.
372 By default it retries until a signature is calculated.
393 given provider side digest signature context I<ctx> and stores them in I<params>.
397 given provider side digest signature context I<ctx> to I<params>.
401 Parameters currently recognised by built-in signature algorithms are the same
414 provider side signature context, or NULL on failure.