Home
last modified time | relevance | path

Searched refs:pairs (Results 1 – 25 of 33) sorted by relevance

12

/openssl-master/util/
A Dc-compress-test.pl10 my @pairs =
41 foreach (@pairs) {
A Dcavs-to-evptest.pl44 my @pairs = split(/, /, $1);
45 foreach my $pair (@pairs) {
/openssl-master/test/testutil/
A Dstanza.c88 PAIR *pp = s->pairs; in test_readstanza()
151 PAIR *pp = s->pairs; in test_clearstanza()
/openssl-master/doc/internal/man3/
A Dossl_DER_w_begin_sequence.pod19 in pairs, as noted by the function names containing the words C<begin>
A DOPTIONS.pod51 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-master/test/recipes/30-test_evp_data/
A Devpmd_sha.txt157 # Others are pairs of "LongMsg" vectors available at
265 # Following tests are pairs of *last* "VariableOut" vectors from
/openssl-master/doc/man3/
A DDH_get_1024_160.pod21 - Create standardized public primes or DH pairs
A DSSL_CTX_set1_sigalgs.pod28 must consist of pairs of NIDs corresponding to digest and public key
A DOSSL_CMP_exec_certreq.pod111 infoType and infoValue pairs (InfoTypeAndValue; short: B<ITAV>)
A DBIO_s_bio.pod42 One typical use of BIO pairs is to place TLS/SSL I/O under application control, this
A DENGINE_add.pod406 OpenSSL. This mechanism is entirely based on the use of name-value pairs
438 name of the ENGINE it wishes to use, a table of string-pairs for use before
440 the string-pairs used for control commands consist of a command "name"
A DSSL_CTX_use_certificate.pod141 key/certificate pairs at a time. The certificate used depends on the
A DEVP_PKEY_new.pod63 (also known as "key pairs"), and can be used for diverse operations, like
/openssl-master/apps/lib/
A Dopt.c464 int opt_pair(const char *name, const OPT_PAIR* pairs, int *result) in opt_pair() argument
468 for (pp = pairs; pp->name; pp++) in opt_pair()
474 for (pp = pairs; pp->name; pp++) in opt_pair()
/openssl-master/Configurations/
A DREADME-design.md206 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-master/apps/include/
A Dopt.h386 int opt_pair(const char *arg, const OPT_PAIR * pairs, int *result);
/openssl-master/test/
A Dparams_conversion_test.c56 const PAIR *pp = s->pairs; in param_conversion_load_stanza()
A Dtestutil.h537 PAIR pairs[TESTMAXPAIRS]; member
/openssl-master/doc/HOWTO/
A Dkeys.txt7 come in pairs, with one half being the public key and the other half
/openssl-master/apps/
A Dspeed.c195 const OPT_PAIR pairs[], unsigned int nbelem) in opt_found() argument
199 for (idx = 0; idx < nbelem; ++idx, pairs++) in opt_found()
200 if (strcmp(name, pairs->name) == 0) { in opt_found()
201 *result = pairs->retval; in opt_found()
206 #define opt_found(value, pairs, result)\ argument
207 opt_found(value, result, pairs, OSSL_NELEM(pairs))
/openssl-master/doc/man7/
A DOSSL_PROVIDER-FIPS.pod235 Conditional test that is run during the generation of key pairs.
A Dprovider-keymgmt.pod65 in tandem with operations that use private/public key pairs.
/openssl-master/doc/internal/man7/
A DEVP_PKEY.pod18 private/public key pairs, but has had other uses as well.
A Dbuild.info.pod520 Collects I<name> / I<value> pairs (or just I<name> with no defined
524 example, these pairs should become C macro definitions whenever a
/openssl-master/doc/man5/
A Dconfig.pod217 containing name/value pairs of OID's.
341 Each configuration section consists of name/value pairs that are parsed

Completed in 42 milliseconds

12