Searched refs:next (Results 151 – 175 of 228) sorted by relevance
12345678910
/openssl/doc/man3/ |
H A D | ASN1_item_d2i_bio.pod | 47 On exit I<*in> will be updated to point to the next byte in the buffer after the
|
H A D | EVP_PKEY_gettable_params.pod | 100 * NB: assumes 'key' is set up before the next step. In this example the key
|
H A D | OSSL_ENCODER_CTX_new_for_pkey.pod | 42 them up, so almost all the caller has to do next is call functions like
|
H A D | OSSL_DECODER_CTX_new_for_pkey.pod | 40 them up, so all the caller has to do next is call functions like
|
H A D | PEM_read.pod | 56 Both skip any non-PEM data that precedes the start of the next PEM object.
|
H A D | BF_encrypt.pod | 65 B<ivec> which needs to be passed along into the next call of the same function
|
H A D | BIO_read.pod | 45 BIO_get_line() attempts to read from BIO I<b> a line of data up to the next '\n'
|
H A D | OSSL_ENCODER_CTX.pod | 76 the input for the next in the chain. The B<OSSL_ENCODER_CTX> holds all the
|
H A D | ENGINE_add.pod | 244 ENGINE list - they will return a new structural reference to the next (or 272 ENGINE_get_default_cipher_engine(), etc. These are discussed in the next 397 That's all that's required. Eg. the next time OpenSSL tries to set up an 544 identifier of a command supported by the ENGINE and returns the next command
|
H A D | OSSL_HPKE_CTX_new.pod | 399 the nonce to the next subsequent call to OSSL_HPKE_open() (but not to 402 nonce increment to be used for the next call. 410 I<seq> output) that will be used in the next call to seal or open. That would
|
H A D | SSL_CTX_add1_chain_cert.pod | 85 the first valid certificate or B<SSL_CERT_SET_NEXT> to set the next valid
|
H A D | SSL_CTX_set_client_hello_cb.pod | 38 of the last call if needed to continue. On the next call into the handshake
|
H A D | DES_random_key.pod | 194 be passed to the next call to this function. Since this function runs 213 be passed to the next call to this function. Since this function runs
|
H A D | DEFINE_STACK_OF.pod | 117 such that the next I<n> calls to B<sk_I<TYPE>_insert>(), B<sk_I<TYPE>_push>() 124 The next I<n> calls to B<sk_I<TYPE>_insert>(), B<sk_I<TYPE>_push>() or
|
/openssl/doc/internal/man3/ |
H A D | DEFINE_PRIORITY_QUEUE_OF.pod | 68 structure such that the next I<n> calls to B<ossl_pqueue_I<TYPE>_push>()
|
H A D | ossl_rcu_lock_new.pod | 100 when the next synchronization completes. Note: It is not guaranteed that the
|
/openssl/crypto/bio/ |
H A D | bio_lib.c | 844 void BIO_set_next(BIO *b, BIO *next) in BIO_set_next() argument 846 b->next_bio = next; in BIO_set_next()
|
/openssl/doc/man7/ |
H A D | ossl-guide-tls-client-non-block.pod | 240 work out what we should do next. Note that we do not expect an EOF to occur at 253 one retry to the next. However, in this case, you must still retry exactly the 336 must call L<SSL_get_error(3)> to work out what to do next. We use our
|
H A D | EVP_KDF-ARGON2.pod | 24 in later slices and next passes it generates them data-dependently as in
|
/openssl/test/ |
H A D | tls-provider.c | 2355 goto next; in xor_der2key_decode() 2369 goto next; in xor_der2key_decode() 2378 goto next; in xor_der2key_decode() 2385 goto next; in xor_der2key_decode() 2405 next: in xor_der2key_decode()
|
H A D | evp_test.c | 68 struct key_list_st *next; member 3500 key->next = private_keys; in keygen_test_run() 3962 for (; lst != NULL; lst = lst->next) { in find_key() 3975 KEY_LIST *next = lst->next; in free_key_list() local 3980 lst = next; in free_key_list() 4204 key->next = *klist; in parse()
|
/openssl/ |
H A D | README-FIPS.md | 40 OpenSSL release to build everything else, then refer to the next section.
|
/openssl/doc/designs/quic-design/ |
H A D | quic-ackm.md | 365 structures, are guaranteed to remain valid until the next call to any 461 so that the next call to `ossl_ackm_get_probe_request` (if made immediately)
|
H A D | tx-packetiser.md | 531 the next active stream every n packets (where n ≥ 1). 540 completing transmission of one stream before beginning the next. However, it 555 revolving round robin basis, moving to the next stream in the round robin 557 fill a packet, we do also move to the next stream, so IRPM can still occur in
|
/openssl/crypto/bn/asm/ |
H A D | bn-c64xplus.asm | 279 ;; chronologically next cycle in *preceding* SPLOOP iteration.
|
Completed in 137 milliseconds
12345678910