Lines Matching refs:input
44 treatment of the input to EVP_PKEY_verify() may be pre-determined, and in that
55 This function enables using algorithms that can process input of arbitrary
66 implementation determine how the input bytes are processed and if there's a
67 limit on the total size of the input. See L</NOTES> below for a deeper
90 Some signature implementations only accumulate the input data and do no
91 further processing before verifying it (they expect the input to be a digest),
99 input, while ED25519 can be expected to process the input with a hash, i.e.
105 like the message digest algorithm that the input is supposed to be digested
113 signature algorithm with a hash algorithm to process the input. In other
134 To allow either way (which may depend on the application's flow of input), the
163 Verify signature using PKCS#1 padding and a SHA256 digest as input:
200 input digest is assumed to have been computed using SHA256.
246 /* in the input in this example. */
248 /* inlen is the length of the input in this example. */
284 /* in is the input in this example. */
286 /* inlen is the length of the input in this example. */
