Searched refs:exact (Results 1 – 25 of 26) sorted by relevance
12
| /openssl-master/doc/man3/ |
| A D | EVP_PKEY_get_size.pod | 32 EVP_PKEY_get_size() is only preliminary and not exact, so the final
54 buffer and still pass a pointer to an integer and get the exact size
57 exact buffer size, then allocate the buffer in between, and call that
|
| A D | OSSL_STORE_SEARCH.pod | 99 This criterion supports a search by exact match of subject name.
106 This criterion supports a search by exact match of both issuer name and serial
116 This criterion supports a search by exact match of key fingerprint.
|
| A D | SSL_clear.pod | 42 handshake). It only makes sense for a new connection with the exact
|
| A D | BIO_f_buffer.pod | 60 BIO_gets() or exact size BIO_read_ex() functionality if the following
|
| A D | BF_encrypt.pod | 72 number of bytes (the amount does not have to be an exact multiple of 8). The
|
| A D | EVP_PKEY_fromdata.pod | 27 The exact key data that the user can pass depends on the key type.
|
| A D | BN_generate_prime.pod | 71 If B<add> is B<NULL> the returned prime number will have exact bit
|
| A D | d2i_RSAPrivateKey.pod | 197 The exact L<OSSL_ENCODER(3)> output is driven by arguments rather than by
|
| A D | EVP_PKEY_ASN1_METHOD.pod | 244 B<sigalg> contains the exact signature algorithm.
|
| /openssl-master/apps/demoSRP/ |
| A D | srp_verifier.txt | 4 # The exact values ... you have to dig this out from the source of srp.c
|
| /openssl-master/crypto/stack/ |
| A D | stack.c | 178 static int sk_reserve(OPENSSL_STACK *st, int n, int exact) in sk_reserve() argument
206 if (!exact) { in sk_reserve()
|
| /openssl-master/doc/man7/ |
| A D | x509.pod | 16 certificate is still valid. The exact definition of those can be
|
| A D | provider-keymgmt.pod | 128 The exact contents of a key object are defined by the provider, and it
130 the exact same structure to represent this collection of data, so that
200 The exact interpretation of those bits or how they combine is left to
|
| A D | openssl-core.h.pod | 44 It's a generic type used as a generic descriptor, its exact meaning
|
| A D | provider-object.pod | 70 The exact target implementation to use is determined from the I<object type>
|
| /openssl-master/test/ssl-tests/ |
| A D | 13-fragmentation.cnf.in | 106 # exact minimum ratio depends on the platform, and is usually
|
| /openssl-master/ |
| A D | configdata.pm.in | 287 build file for more exact data:
|
| A D | NOTES-UNIX.md | 84 your system, please refer to ld(1) for the exact information on your
|
| /openssl-master/doc/internal/man3/ |
| A D | OSSL_METHOD_STORE.pod | 45 It's left to the caller to define the exact contents.
|
| /openssl-master/crypto/property/ |
| A D | README.md | 89 collection does not have to be exact.
|
| /openssl-master/doc/internal/man7/ |
| A D | build.info.pod | 184 the exact interpretation of those attributes is entirely up to them
480 I<item> (in other words, we use the exact same style of
|
| /openssl-master/crypto/bn/ |
| A D | README.pod | 182 B<BN_MULL_SIZE_NORMAL> and the size is an exact multiple of the word
|
| /openssl-master/doc/man1/ |
| A D | openssl-enc.pod.in | 148 If this option is used while encrypting, the same exact value will be needed
|
| A D | openssl-ca.pod.in | 529 several valid certificate entries may have the exact same subject.
|
| /openssl-master/Configurations/ |
| A D | README.md | 433 There may also be cases where the exact file isn't easily specified,
|
Completed in 26 milliseconds
12