Searched refs:hold (Results 1 – 25 of 43) sorted by relevance
12
/openssl/doc/man3/ |
H A D | DH_size.pod | 42 B<dh> doesn't hold any key parameters. 45 B<dh> doesn't hold any key parameters. 48 B<dh> doesn't hold any key parameters.
|
H A D | DSA_size.pod | 40 I<dsa> doesn't hold any key parameters. 43 hold any key parameters. 46 hold any key parameters.
|
H A D | BIO_connect.pod | 96 will hold the error data and errno has the system error. 99 When an error has occurred, the OpenSSL error stack will hold the error 104 OpenSSL error stack will hold the error data and errno has the system
|
H A D | BIO_ADDRINFO.pod | 53 used. B<res> points at a pointer to hold the start of a B<BIO_ADDRINFO> 57 parameter and expects the B<host> parameter to hold the path to the socket file.
|
H A D | EVP_PKEY_new.pod | 62 B<EVP_PKEY> is a generic structure to hold diverse types of asymmetric keys 68 Conceptually, an B<EVP_PKEY> internal key may hold a private key, a public 137 the number of bytes required to hold the key. The calling application is 147 the number of bytes required to hold the key. The calling application is
|
H A D | EVP_PKEY_gettable_params.pod | 87 EVP_PKEY_get_octet_string_param() if I<max_buf_sz> is not big enough to hold the 89 buffer size to hold the value.
|
H A D | CMS_uncompress.pod | 43 The lack of single pass processing and the need to hold all data in memory as
|
H A D | PKCS7_decrypt.pod | 41 The lack of single pass processing and need to hold all data in memory as
|
H A D | SMIME_read_PKCS7.pod | 59 The use of a memory BIO to hold the signed content limits the size
|
H A D | RSA_private_encrypt.pod | 56 B<rsa>. B<to> must point to a memory section large enough to hold the
|
H A D | BN_CTX_new.pod | 33 but uses the secure heap (see L<CRYPTO_secure_malloc(3)>) to hold the
|
H A D | OSSL_CMP_ITAV_set0.pod | 30 e.g., in the generalInfo PKIHeader field, to hold a key-value pair.
|
H A D | SMIME_read_CMS.pod | 61 The use of a memory BIO to hold the signed content limits the size of message
|
H A D | SMIME_read_ASN1.pod | 55 The use of a memory BIO to hold the signed content limits the size of message
|
H A D | EVP_SignInit.pod | 66 This requirement does not hold for RSA signatures.
|
H A D | SSL_new.pod | 17 SSL_new() creates a new B<SSL> structure which is needed to hold the
|
H A D | RSA_public_encrypt.pod | 71 to a memory section large enough to hold the maximal possible decrypted
|
H A D | CMS_decrypt.pod | 85 The lack of single pass processing and the need to hold all data in memory as
|
H A D | PKCS7_verify.pod | 113 The lack of single pass processing and need to hold all data in memory as
|
H A D | SSL_CTX_set_mode.pod | 87 then release the memory we were using to hold it.
|
H A D | SSL_CTX_set_tmp_dh_callback.pod | 47 even if they get hold of the normal (certified) key, as this key was
|
/openssl/apps/ |
H A D | ca.c | 2466 ASN1_OBJECT *hold = NULL; in make_revoked() local 2472 i = unpack_revinfo(&revDate, &reason_code, &hold, &comp_time, str); in make_revoked() 2493 if (rev && hold) { in make_revoked() 2495 (rev, NID_hold_instruction_code, hold, 0, 0) <= 0) in make_revoked() 2507 ASN1_OBJECT_free(hold); in make_revoked() 2564 ASN1_OBJECT *hold = NULL; in unpack_revinfo() local 2619 hold = OBJ_txt2obj(arg_str, 0); in unpack_revinfo() 2621 if (!hold) { in unpack_revinfo() 2626 *phold = hold; in unpack_revinfo() 2628 ASN1_OBJECT_free(hold); in unpack_revinfo()
|
/openssl/crypto/perlasm/ |
H A D | README.md | 54 So how does this all hold together? Given
|
/openssl/crypto/ |
H A D | README-sparse_array.md | 75 node. It then creates a second second level node to hold the pointer to the
|
/openssl/doc/man5/ |
H A D | fips_config.pod | 10 is used to hold information about the FIPS module. This includes a digest
|
Completed in 63 milliseconds
12