Searched refs:place (Results 1 – 25 of 68) sorted by relevance
123
/openssl/crypto/bio/ |
H A D | bio_print.c | 441 int place = 0; in fmtint() local 467 convert[place++] = (caps ? "0123456789ABCDEF" : "0123456789abcdef") in fmtint() 470 } while (uvalue && (place < (int)sizeof(convert))); in fmtint() 471 if (place == sizeof(convert)) in fmtint() 472 place--; in fmtint() 473 convert[place] = 0; in fmtint() 475 zpadlen = max - place; in fmtint() 477 min - OSSL_MAX(max, place) - (signvalue ? 1 : 0) - strlen(prefix); in fmtint() 517 while (place > 0) { in fmtint() 518 if (!doapr_outch(sbuffer, buffer, currlen, maxlen, convert[--place])) in fmtint()
|
/openssl/doc/man3/ |
H A D | SSL_key_update.pod | 37 update will not take place until the next time an IO operation such as 38 SSL_read_ex() or SSL_write_ex() takes place on the connection. Alternatively 39 SSL_do_handshake() can be called to force the update to take place immediately. 52 such as SSL_read_ex() or SSL_write_ex() takes place on the connection a check
|
H A D | SSL_library_init.pod | 25 SSL_library_init() must be called before any other action takes place.
|
H A D | BIO_s_bio.pod | 42 One typical use of BIO pairs is to place TLS/SSL I/O under application control, this 49 Calls to BIO_write_ex() will place data in the buffer or request a retry if the 114 TLS/SSL handshake for example. BIO_write_ex() will succeed and place data in the
|
H A D | BUF_MEM_new.pod | 47 is NULL, the array is reversed in-place.
|
H A D | OPENSSL_config.pod | 27 no configuration takes place.
|
H A D | SSL_get0_peer_rpk.pod | 39 Raw public keys are used in place of certificates when the option is
|
H A D | SSL_do_handshake.pod | 15 SSL_do_handshake() will wait for an SSL/TLS handshake to take place. If the
|
H A D | X509_digest.pod | 66 to a place where the digest size will be stored.
|
H A D | SSL_CTX_set_cert_store.pod | 46 the verification takes place. So will e.g. the verify_callback() be
|
H A D | EVP_PKEY_CTX_set_rsa_pss_keygen_md.pod | 60 restricts the digest and MGF1 algorithms. If any restrictions are in place
|
H A D | MD5.pod | 56 of the B<n> bytes at B<d> and place it in B<md> (which must have space
|
H A D | SSL_get_client_random.pod | 59 in place of RAND_bytes() would be grossly foolish.
|
H A D | SSL_set1_host.pod | 55 is cleared or freed, or a renegotiation takes place. Applications
|
H A D | SSL_CTX_set_cipher_list.pod | 75 in). Thus no syntax checking takes place. Items that are not recognized, because
|
/openssl/test/recipes/90-test_includes_data/conf-includes/ |
H A D | includes1.cnf | 18 new_certs_dir = $dir/new_certs # default place for new certs.
|
/openssl/ |
H A D | SUPPORT.md | 10 In this case the [openssl-users] mailing list is the right place for you. 82 is now taking place in the form of GitHub pull requests. Although not active
|
H A D | CONTRIBUTING.md | 28 mistake), then place the text "`CLA: trivial`" on a line by itself below 40 It is not sufficient to only place the text "`CLA: trivial`" in the GitHub
|
/openssl/test/ |
H A D | test.cnf | 13 new_certs_dir = $dir/new_certs # default place for new certs.
|
H A D | CAtsa.cnf | 31 new_certs_dir = $dir/newcerts # default place for new certs.
|
/openssl/crypto/err/ |
H A D | README.md | 37 generation script as the point to place new error codes, any text
|
/openssl/doc/man7/ |
H A D | openssl_user_macros.pod.in | 78 place:
|
/openssl/doc/internal/man3/ |
H A D | OSSL_SAFE_MATH_SIGNED.pod | 35 undefined as per the C standard will take place.
|
/openssl/VMS/ |
H A D | openssl_startup.com.in | 75 $ ! Check that things are in place, and specifically, the stuff
|
/openssl/crypto/engine/ |
H A D | README.md | 150 that is unset only if un/registration takes place on that pile. Ie. if 156 "initialisation" will take place). 188 place. ENGINE_cleanup() will simply iterate across a list of registered cleanup
|
Completed in 35 milliseconds
123