| /openssl/crypto/ |
| H A D | riscvcap.c | 81 static long riscv_hwprobe(struct riscv_hwprobe *pairs, size_t pair_count, in riscv_hwprobe() argument
85 return syscall(__NR_riscv_hwprobe, pairs, pair_count, cpu_count, cpus, flags); in riscv_hwprobe()
91 struct riscv_hwprobe pairs[OSSL_RISCV_HWPROBE_PAIR_COUNT] = { in hwprobe_to_cap() local
95 ret = riscv_hwprobe(pairs, OSSL_RISCV_HWPROBE_PAIR_COUNT, 0, NULL, 0); in hwprobe_to_cap()
100 if (pairs[j].key == RISCV_capabilities[i].hwprobe_key in hwprobe_to_cap()
101 && (pairs[j].value & RISCV_capabilities[i].hwprobe_value) in hwprobe_to_cap()
|
| /openssl/util/ |
| H A D | c-compress-test.pl | 10 my @pairs =
41 foreach (@pairs) {
|
| H A D | cavs-to-evptest.pl | 44 my @pairs = split(/, /, $1);
45 foreach my $pair (@pairs) {
|
| /openssl/test/testutil/ |
| H A D | stanza.c | 88 PAIR *pp = s->pairs; in test_readstanza()
149 PAIR *pp = s->pairs; in test_clearstanza()
|
| /openssl/doc/internal/man3/ |
| H A D | ossl_DER_w_begin_sequence.pod | 19 in pairs, as noted by the function names containing the words C<begin>
|
| H A D | OPTIONS.pod | 51 int opt_pair(const char *name, const OPT_PAIR* pairs, int *result);
282 The opt_pair() function takes a list of I<pairs>, each of which
|
| /openssl/test/recipes/30-test_evp_data/ |
| H A D | evpmd_sha.txt | 176 # Others are pairs of "LongMsg" vectors available at
284 # Following tests are pairs of *last* "VariableOut" vectors from
|
| /openssl/doc/man3/ |
| H A D | DH_get_1024_160.pod | 21 - Create standardized public primes or DH pairs
|
| H A D | SSL_CTX_set1_sigalgs.pod | 28 must consist of pairs of NIDs corresponding to digest and public key
|
| 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
|
| H A D | ENGINE_add.pod | 407 OpenSSL. This mechanism is entirely based on the use of name-value pairs
439 name of the ENGINE it wishes to use, a table of string-pairs for use before
441 the string-pairs used for control commands consist of a command "name"
|
| H A D | EVP_PKEY_new.pod | 63 (also known as "key pairs"), and can be used for diverse operations, like
|
| H A D | SSL_CTX_use_certificate.pod | 142 key/certificate pairs at a time. The certificate used depends on the
|
| H A D | OSSL_CMP_exec_certreq.pod | 132 infoType and infoValue pairs (InfoTypeAndValue; short: B<ITAV>)
|
| /openssl/apps/lib/ |
| H A D | opt.c | 494 int opt_pair(const char *name, const OPT_PAIR* pairs, int *result) in opt_pair() argument
498 for (pp = pairs; pp->name; pp++) in opt_pair()
504 for (pp = pairs; pp->name; pp++) in opt_pair()
|
| /openssl/Configurations/ |
| H A D | README-design.md | 206 pairs. These are directly inferred from the DEPEND
213 pairs. These are directly inferred from the GENERATE
217 pairs. These are directly inferred from the INCLUDE
220 install => a hash table containing 'type' => [ 'file' ... ] pairs.
235 pairs. These are indirectly inferred from the SOURCE
|
| /openssl/apps/include/ |
| H A D | opt.h | 426 int opt_pair(const char *arg, const OPT_PAIR *pairs, int *result);
|
| /openssl/test/ |
| H A D | params_conversion_test.c | 52 const PAIR *pp = s->pairs; in param_conversion_load_stanza()
|
| H A D | testutil.h | 592 PAIR pairs[TESTMAXPAIRS]; member
|
| /openssl/doc/HOWTO/ |
| H A D | keys.txt | 7 come in pairs, with one half being the public key and the other half
|
| /openssl/apps/ |
| H A D | speed.c | 220 const OPT_PAIR pairs[], unsigned int nbelem) in opt_found() argument
224 for (idx = 0; idx < nbelem; ++idx, pairs++) in opt_found()
225 if (strcmp(name, pairs->name) == 0) { in opt_found()
226 *result = pairs->retval; in opt_found()
231 #define opt_found(value, pairs, result)\ argument
232 opt_found(value, result, pairs, OSSL_NELEM(pairs))
|
| /openssl/doc/designs/quic-design/ |
| H A D | connection-id-cache.md | 57 An alternative would be receiving from <host address, source port> pairs.
|
| /openssl/doc/internal/man7/ |
| H A D | EVP_PKEY.pod | 18 private/public key pairs, but has had other uses as well.
|
| H A D | build.info.pod | 553 Collects I<name> / I<value> pairs (or just I<name> with no defined
557 example, these pairs should become C macro definitions whenever a
|
| /openssl/doc/man5/ |
| H A D | config.pod | 217 containing name/value pairs of OID's.
352 Each configuration section consists of name/value pairs that are parsed
|
