Searched refs:behavior (Results 1 – 25 of 31) sorted by relevance
12
/openssl/test/ |
H A D | lhash_test.c | 550 char behavior; in do_mt_hash_work() local 563 behavior = (char)(test_random() % NUM_BEHAVIORS); in do_mt_hash_work() 574 switch(behavior) { in do_mt_hash_work() 590 if (behavior == DO_REPLACE) { in do_mt_hash_work() 602 giter, expected_rc, behavior == DO_REPLACE ? "replace" : "insert", in do_mt_hash_work()
|
/openssl/doc/man3/ |
H A D | SSL_CTX_set_record_padding_callback.pod | 86 The default behavior is to add no padding to the record. 88 A user-supplied padding callback function will override the behavior set by 90 callback to NULL will restore the configured block padding behavior.
|
H A D | PEM_read_bio_ex.pod | 32 the historical behavior of PEM_read_bio().
|
H A D | BIO_s_fd.pod | 48 The behaviour of BIO_read_ex() and BIO_write_ex() depends on the behavior of the
|
H A D | EVP_DigestVerifyInit.pod | 158 this behavior by setting the EVP_MD_CTX_FLAG_FINALISE context flag via 175 functions can lead to subsequent undefined behavior when calling
|
H A D | EVP_VerifyInit.pod | 66 behavior by setting the EVP_MD_CTX_FLAG_FINALISE context flag via
|
H A D | EVP_DigestSignInit.pod | 168 Applications may disable this behavior by setting the EVP_MD_CTX_FLAG_FINALISE 186 functions can lead to subsequent undefined behavior when calling
|
H A D | SSL_CTX_set1_curves.pod | 72 with, e.g., a post-quantum algorithm, this behavior may allow a network attacker 176 However, OpenSSL's behavior as a TLS 1.3 server is to consider I<all>
|
H A D | SSL_CTX_set_client_cert_cb.pod | 50 server. This constraint is violated by the default behavior of the OpenSSL
|
H A D | EVP_SignInit.pod | 70 behavior by setting the EVP_MD_CTX_FLAG_FINALISE context flag via
|
H A D | BIO_f_base64.pod | 26 This behavior can be changed with B<BIO_FLAGS_BASE64_NO_NL> flag.
|
H A D | X509_check_host.pod | 66 currently no B<flags> that would affect the behavior of this call.
|
H A D | SSL_CTX_set_client_hello_cb.pod | 100 not use a servername callback, in order to avoid unexpected behavior that
|
H A D | X509_STORE_add_cert.pod | 90 behavior is documented in the corresponding B<X509_VERIFY_PARAM> manual
|
H A D | X509_dup.pod | 453 use; use NULL to get the default behavior. If a print function is
|
H A D | PKCS7_verify.pod | 47 The default behavior allows this, for compatibility with older
|
H A D | OSSL_CMP_CTX_new.pod | 224 after receiving a response, which is the default behavior for HTTP 1.0. 319 B<WARNING:> This setting leads to unspecified behavior and it is meant 333 B<WARNING:> This setting leads to unspecified behavior and it is meant
|
H A D | OPENSSL_malloc.pod | 140 behaviors listed in the POSIX documentation, with the additional behavior that
|
H A D | OSSL_HTTP_REQ_CTX.pod | 127 kept open after receiving a response. This is the default behavior for HTTP 1.0.
|
H A D | OSSL_HTTP_transfer.pod | 201 after receiving a response, which is the default behavior for HTTP 1.0.
|
/openssl/external/perl/Text-Template-1.56/ |
H A D | Changes | 228 - Fixed a bug in the way backslashes were processed. The 1.10 behavior was 231 evaluation.) The new behavior is also incompatible with the beta 234 - Documentation for the new behavior, and tests for the bug. 295 - BROKEN function behavior is rationalized. You can now pass an
|
/openssl/ |
H A D | NOTES-VALGRIND.md | 25 Test behavior can be modified by adjusting environment variables.
|
H A D | NOTES-WINDOWS.md | 130 A summary table of behavior on Windows platforms
|
/openssl/doc/man5/ |
H A D | config.pod | 62 The default behavior, where the B<value> is B<false> or B<off>, is to allow 68 as a regular character in symbol names. Supporting this behavior can be 73 The default behavior, where the B<value> is B<false> or B<off>, is to treat
|
/openssl/doc/man1/ |
H A D | openssl-cmp.pod.in | 428 B<WARNING:> This leads to behavior violating RFC 4210. 572 (which would be the default behavior of HTTP 1.0) 684 B<WARNING:> This setting leads to unspecified behavior and it is meant 1263 WARNING: This setting leads to behavior violating RFC 4210.
|
Completed in 29 milliseconds
12