Searched refs:process (Results 1 – 25 of 101) sorted by relevance
12345
/openssl-master/doc/man3/ |
A D | OPENSSL_fork_prepare.pod | 27 OpenSSL has state that should be reset when a process forks. For example, 45 process should call OPENSSL_fork_parent() and the child process should
|
A D | PEM_read_bio_PrivateKey.pod | 237 The B<PUBKEY> functions process a public key using an EVP_PKEY 246 The B<RSAPublicKey> functions process an RSA public key using an 250 The B<RSA_PUBKEY> functions also process an RSA public key using 255 The B<DSAPrivateKey> functions process a DSA private key using a 260 The B<DSA_PUBKEY> functions process a DSA public key using 271 The B<DSAparams> functions process DSA parameters using a DSA 275 The B<DHparams> functions process DH parameters using a DH 279 The B<X509> functions process an X509 certificate using an X509 280 structure. They will also process a trusted X509 certificate but 286 The B<X509_REQ> and B<X509_REQ_NEW> functions process a PKCS#10 [all …]
|
A D | SSL_CTX_set_verify.pod | 78 certificate verification process can be checked after the TLS/SSL handshake 85 The certificate returned (if any) is checked. If the verification process 93 B<Client mode:> the server certificate is verified. If the verification process 173 verification process. If B<verify_callback> returns 0, the verification 174 process is immediately stopped with "verification failed" state. If 177 the verification process is continued. If B<verify_callback> always returns 179 failures and the connection will be established. The calling process can
|
A D | OSSL_DECODER_from_bio.pod | 30 OSSL_DECODER_from_data() runs the decoding process for the context I<ctx>, 36 OSSL_DECODER_from_bio() runs the decoding process for the context I<ctx>,
|
A D | OSSL_ENCODER_to_bio.pod | 30 OSSL_ENCODER_to_data() runs the encoding process for the context I<ctx>, 41 OSSL_ENCODER_to_bio() runs the encoding process for the context I<ctx>, with
|
A D | ASN1_item_d2i_bio.pod | 36 during the process then they will use the B<OSSL_LIB_CTX>provided in the 49 algorithm fetches are required during the process then they will use the
|
A D | SSL_CTX_set_cert_verify_callback.pod | 49 This process may even be repeated if need be. 74 B<verify_callback> function called during the verification process. The
|
A D | OSSL_STORE_attach.pod | 22 should be used to process the data. The reference count of the B<BIO> object
|
A D | ASN1_item_new.pod | 20 required during the process then they will use the B<OSSL_LIB_CTX> provided in
|
A D | SSL_write.pod | 53 call to a write function can also cause read operations! The calling process 107 closed, an error occurred or action must be taken by the calling process. 129 closed, an error occurred or action must be taken by the calling process.
|
A D | BIO_s_connect.pod | 91 non blocking I/O is set during the connect process. 123 so to separate the connection process from other I/O processing. 129 connection process with the reason BIO_RR_CONNECT. If this is returned
|
A D | SSL_shutdown.pod | 33 This way resources can be saved, as the process can already terminate or 40 to resume the session because it did not received and process the session ticket 61 B<SSL_ERROR_WANT_WRITE>. The calling process then must repeat the call after
|
A D | X509_get0_distinguishing_id.pod | 27 an entity in the authentication process.
|
A D | OSSL_PARAM_dup.pod | 20 duplicated and merged with other B<OSSL_PARAM> to assist in this process.
|
A D | SSL_CTX_set_mode.pod | 64 B<SSL_MODE_AUTO_RETRY> causes it to try to process the next record instead of 69 Setting B<SSL_MODE_AUTO_RETRY> for a nonblocking B<BIO> will process
|
A D | BIO_should_retry.pod | 101 can occur during the initial handshake process. 104 structure cannot process or return any data. This depends on the behaviour of
|
A D | X509_STORE_add_cert.pod | 56 Details of the chain building and checking process are described in 70 and verification operation. That process includes providing the end-entity
|
A D | SSL_CTX_load_verify_locations.pod | 36 Details of the certificate verification and chain checking process are 93 Details of the chain building process are described in
|
A D | CMS_get0_type.pod | 19 an ASN1_OBJECT pointer. An application can then decide how to process the
|
A D | SSL_do_handshake.pod | 32 B<SSL_ERROR_WANT_WRITE>. The calling process then must repeat the call after
|
/openssl-master/apps/ |
A D | storeutl.c | 19 static int process(const char *uri, const UI_METHOD *uimeth, PW_CB_DATA *uidata, 321 ret = process(argv[0], get_ui_method(), &pw_cb_data, in storeutl_main() 352 static int process(const char *uri, const UI_METHOD *uimeth, PW_CB_DATA *uidata, in process() function 442 ret += process(suburi, uimeth, uidata, in process()
|
/openssl-master/engines/ |
A D | e_loader_attic.txt | 18 ui process interrupted or cancelled
|
/openssl-master/doc/man7/ |
A D | provider-decoder.pod | 67 can be called as the final step of the decoding process. 242 This means "carry on the decoding process", and is meaningful even though 251 This means "stop the decoding process", and is meaningful when the input 258 The conditions to stop the decoding process are at the discretion of the 292 OSSL_FUNC_decoder_decode() returns 1 to signal that the decoding process
|
/openssl-master/ |
A D | HACKING.md | 32 To aid in this process the generated files can be committed separately
|
/openssl-master/VMS/ |
A D | openssl_ivp.com.in | 4 $ ! It had better be spawned, as it creates process logicals
|
Completed in 34 milliseconds
12345