Home
last modified time | relevance | path

Searched refs:what (Results 1 – 25 of 115) sorted by relevance

12345

/openssl/
H A Dconfigdata.pm.in265 foreach my $what (@disablables) {
266 $longest = length($what) if $longest < length($what);
267 $longest2 = length($disabled{$what})
268 if $disabled{$what} && $longest2 < length($disabled{$what});
271 foreach my $what (@disablables) {
272 print " $what\n" unless $disabled{$what};
275 foreach my $what (@disablables) {
276 if ($disabled{$what}) {
277 print " $what", ' ' x ($longest - length($what) + 1),
278 "[$disabled{$what}]", ' ' x ($longest2 - length($disabled{$what}) + 1);
[all …]
H A DConfigure1793 foreach my $what (sort keys %disabled) {
1796 next if $deprecated_disablables{$what};
1799 next if $what =~ m|^deprecated-|;
1801 $config{options} .= " no-$what";
1806 (my $WHAT = uc $what) =~ s|-|_|g;
1807 my $skipdir = $what;
1810 $skipdir = "ripemd" if $what eq "rmd160";
1816 $skipdir{engines} = $what if $what eq 'engine';
1817 $skipdir{"crypto/$skipdir"} = $what
1818 unless $what eq 'async' || $what eq 'err' || $what eq 'dso';
[all …]
/openssl/test/
H A Dtiming_load_creds.c63 static void print_timeval(const char *what, struct timeval *tp) in print_timeval() argument
65 printf("%s %d sec %d microsec\n", what, (int)tp->tv_sec, (int)tp->tv_usec); in print_timeval()
84 int i, debug = 0, count = 100, what = 'c'; in main() local
114 what = *optarg; in main()
147 switch (what) { in main()
166 switch (what) { in main()
/openssl/test/testutil/
H A Dapps_shims.c16 void *app_malloc(size_t sz, const char *what) in app_malloc() argument
26 TEST_info("Could not allocate %zu bytes for %s\n", sz, what); in app_malloc()
/openssl/doc/man1/
H A Dopenssl-list.pod.in64 The options below where verbosity applies say a bit more about what that means.
105 information on what parameters each implementation supports.
124 information on what parameters each implementation supports.
133 information on what parameters each implementation supports.
198 of what type of parameter it takes, if any.
/openssl/doc/internal/man3/
H A Dossl_algorithm_do_all.pod41 possibly display of what has been discovered, for example an
42 application that wants to display the loaded providers and what they
/openssl/tools/
H A Dc_rehash.in236 my $what = $is_cert ? 'certificate' : 'CRL';
237 print STDERR "WARNING: Skipping duplicate $what $fname\n";
/openssl/apps/lib/
H A Dapps_ui.c152 static void *ui_malloc(int sz, const char *what) in ui_malloc() argument
157 BIO_printf(bio_err, "Could not allocate %d bytes for %s\n", sz, what); in ui_malloc()
/openssl/doc/man3/
H A DEVP_PKEY_copy_parameters.pod72 what they both contain.
78 Exactly what is compared is ultimately at the discretion of the provider
79 that holds the key, as they will compare what makes sense to them that fits
H A DEVP_KDF.pod113 The set of parameters given with I<params> determine exactly what
120 The set of parameters given with I<params> determine exactly what
127 The set of parameters given with I<params> determine exactly what
131 Also, what happens when a needed parameter isn't passed down is
219 cipher, these parameters set what the algorithm should be.
240 The length must never exceed what can be given with a B<size_t>.
253 The memory size must never exceed what can be given with a B<size_t>.
H A DOSSL_STORE_expect.pod8 - Specify what object type is expected
22 OSSL_STORE_expect() helps applications filter what OSSL_STORE_load() returns
H A DOSSL_ENCODER_CTX_new_for_pkey.pod44 encoding, and I<selection> can be used to select what parts of the I<pkey>
63 OSSL_ENCODER_CTX_set_cipher() tells the implementation what cipher
115 determine what makes sense to include in the output, and this may depend on
H A DOSSL_DECODER_CTX.pod87 figure out what the input data is and to attempt to unpack it into one of
102 what type of input they have. In this case, OSSL_DECODER_from_bio() will
104 discover what kind of input the caller gave it.
142 the input is expected to have. This may be used to determines what decoder
H A DEVP_PKEY_is_a.pod72 The loaded providers and what key types they support will ultimately
73 determine what I<name> is possible to use with EVP_PKEY_is_a(). We do know
H A DX509_LOOKUP.pod111 I<type> indicates what type of object is expected.
121 I<type> indicates what type of object is expected.
203 Otherwise, it returns what the control function in the
221 Otherwise, they return what the corresponding function in the
H A DOSSL_STORE_LOADER.pod176 Furthermore, this function is expected to initialize what needs to be
199 along with what I<args> are expected with each of them.
212 identity I<expected>, and is used to tell the loader what object type is
221 B<OSSL_STORE_SEARCH> search criterion, and is used to tell the loader what
260 close or shut down what needs to be closed, and finally free the
H A DEVP_MAC.pod158 To figure out what the output length will be and allocate space for it
168 The set of parameters given with I<params> determine exactly what
175 The set of parameters given with I<params> determine exactly what
182 The set of parameters given with I<params> determine exactly what
187 Also, what happens when a needed parameter isn't passed down is
301 digest, these parameters set what the algorithm should be.
315 what can be given with a B<size_t>.
/openssl/doc/man7/
H A Dopenssl-core.h.pod27 providers to describe what functionality one side provides to the
55 OpenSSL libraries to describe what algorithms the providers provide
56 implementations of, and with what properties.
H A Dprovider-decoder.pod119 This property is used to specify what format of input the implementation
180 treat separately or together. It's possible to specify what subsets are to
183 This set of bits depend entirely on what kind of provider-side object is
230 if relevant, should determine what the input data should contain.
273 prompt. This could be used to give the user information on what kind
H A Dprovider-encoder.pod136 This property is used to specify what type of output the implementation
187 treat separately or together. It's possible to specify what subsets are to
190 This set of bits depend entirely on what kind of provider-side object is
244 if relevant, should determine in greater detail what will be output.
293 prompt. This could be used to give the user information on what kind
/openssl/doc/HOWTO/
H A Dcertificates.txt6 How you handle certificates depends a great deal on what your role is.
46 signing request", since that's exactly what they do, they sign it and
92 applications, this may be perfectly OK, it all depends on what they
/openssl/dev/release-aux/
H A DREADME.md21 that instructs it what update to do.
/openssl/test/recipes/30-test_evp_data/
H A Devpmac_sm3.txt36 Input = "what do ya want for nothing?"
/openssl/Configurations/
H A Dcommon0.tmpl7 # need to extrapolate exactly what we need to generate. The way to do
H A DINTERNALS.Configure10 who decide to dive into Configure and what it does. This is a living
38 Instead of trying to describe in words, here are some example of what

Completed in 103 milliseconds

12345