Searched refs:exact (Results 1 – 25 of 39) sorted by relevance
12
/openssl/doc/man3/ |
H A D | EVP_PKEY_get_size.pod | 33 EVP_PKEY_get_size() is only preliminary and not exact, so the final 57 buffer and still pass a pointer to an integer and get the exact size 60 exact buffer size, then allocate the buffer in between, and call that
|
H A D | OSSL_STORE_SEARCH.pod | 100 This criterion supports a search by exact match of subject name. 107 This criterion supports a search by exact match of both issuer name and serial 117 This criterion supports a search by exact match of key fingerprint.
|
H A D | OSSL_ITEM.pod | 20 It's a generic type used as a generic descriptor, its exact meaning
|
H A D | BN_set_bit.pod | 39 this error can be safely ignored. Use L<BN_num_bits(3)> to determine the exact
|
H A D | SSL_clear.pod | 45 handshake). It only makes sense for a new connection with the exact
|
H A D | BIO_f_buffer.pod | 60 BIO_gets() or exact size BIO_read_ex() functionality if the following
|
H A D | SSL_handle_events.pod | 16 exact operations performed by SSL_handle_events() vary depending on what kind of protocol
|
H A D | BF_encrypt.pod | 72 number of bytes (the amount does not have to be an exact multiple of 8). The
|
H A D | EVP_PKEY_fromdata.pod | 27 The exact key data that the user can pass depends on the key type.
|
H A D | BN_generate_prime.pod | 73 If B<add> is B<NULL> the returned prime number will have exact bit
|
H A D | d2i_RSAPrivateKey.pod | 195 The exact L<OSSL_ENCODER(3)> output is driven by arguments rather than by
|
/openssl/apps/demoSRP/ |
H A D | srp_verifier.txt | 4 # The exact values ... you have to dig this out from the source of srp.c
|
/openssl/.github/ISSUE_TEMPLATE/ |
H A D | bug_report.md | 23 as well as a log of all errors. Don't forget to include the exact
|
/openssl/crypto/stack/ |
H A D | stack.c | 177 static int sk_reserve(OPENSSL_STACK *st, int n, int exact) in sk_reserve() argument 205 if (!exact) { in sk_reserve()
|
/openssl/doc/man7/ |
H A D | x509.pod | 16 certificate is still valid. The exact definition of those can be
|
H A D | provider-keymgmt.pod | 137 The exact contents of a key object are defined by the provider, and it 139 the exact same structure to represent this collection of data, so that 209 The exact interpretation of those bits or how they combine is left to
|
H A D | provider-object.pod | 70 The exact target implementation to use is determined from the I<object type>
|
H A D | ossl-guide-tls-client-non-block.pod | 51 exact details on how to do this can differ from one platform to another. 304 * that it is NUL terminated so we use fwrite() to write the exact
|
/openssl/test/ssl-tests/ |
H A D | 13-fragmentation.cnf.in | 106 # exact minimum ratio depends on the platform, and is usually
|
/openssl/crypto/property/ |
H A D | README.md | 89 collection does not have to be exact.
|
/openssl/ |
H A D | configdata.pm.in | 339 build file for more exact data:
|
H A D | NOTES-UNIX.md | 84 your system, please refer to ld(1) for the exact information on your
|
/openssl/doc/internal/man3/ |
H A D | OSSL_METHOD_STORE.pod | 49 It's left to the caller to define the exact contents.
|
/openssl/doc/designs/ |
H A D | passing-algorithmidentifier-parameters.md | 40 This way, these parameters can be used in the exact same manner with other
|
/openssl/doc/internal/man7/ |
H A D | build.info.pod | 184 the exact interpretation of those attributes is entirely up to them 477 I<item> (in other words, we use the exact same style of
|
Completed in 73 milliseconds
12