Lines Matching refs:signature
283 The core_obj_add_sigid() function registers a new composite signature algorithm
284 (I<sign_name>) consisting of an underlying signature algorithm (I<pkey_name>)
286 the OIDs for the composite signature algorithm as well as for the underlying
287 signature and digest algorithms are either already known to OpenSSL or have been
292 signature algorithm already exists (even if registered against a different
293 underlying signature or digest algorithm). For I<digest_name>, NULL or an
294 empty string is permissible for signature algorithms that do not need a digest
643 TLS signature algorithms that a provider can support. Each signature supported
645 signature algorithms.
646 TLS1.3 clients can advertise the list of TLS signature algorithms they support
649 to the list of signature algorithms that libssl already supports with
652 Each TLS signature algorithm that a provider supports should be described via
660 The name of the signature algorithm as given in the IANA TLS Signature Scheme
672 A name for the full (possibly composite hash-and-signature) signature
674 The provider may, but is not obligated to, provide a signature implementation
676 signature algorithm and a hash algorithm, which must be given with the
691 The name of the pure signature algorithm that is part of a composite
743 defines the security strength. If the signature algorithm implements its own
753 versions supported by the signature algorithm. The values equate to the
756 there is no defined minimum or maximum. A -1 indicates that the signature
788 * To ensure we get the function signature right, forward declare
