/openssl/ |
H A D | configdata.pm.in | 265 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 D | Configure | 1906 foreach my $what (sort keys %disabled) { 1909 next if $deprecated_disablables{$what}; 1912 next if $what =~ m|^deprecated-|; 1914 $config{options} .= " no-$what"; 1919 (my $WHAT = uc $what) =~ s|-|_|g; 1920 my $skipdir = $what; 1923 $skipdir = "ripemd" if $what eq "rmd160"; 1929 $skipdir{engines} = $what if $what eq 'engine'; 1930 $skipdir{"crypto/$skipdir"} = $what 1931 unless $what eq 'async' || $what eq 'err' || $what eq 'dso'; [all …]
|
/openssl/test/ |
H A D | timing_load_creds.c | 78 static void print_timeval(const char *what, struct timeval *tp) in print_timeval() argument 80 printf("%s %d sec %d microsec\n", what, (int)tp->tv_sec, (int)tp->tv_usec); in print_timeval() 100 int i, debug = 0, count = 100, what = 'c'; in main() local 130 what = *optarg; in main() 163 switch (what) { in main() 182 switch (what) { in main()
|
/openssl/test/testutil/ |
H A D | apps_shims.c | 16 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/man3/ |
H A D | SSL_set1_server_cert_type.pod | 43 These extensions let each side know what its peer is able to accept. 46 what certificate types the client is able to present. 50 The server ultimately chooses what type to request (if any) from the values 56 what certificate types the client accepts. 60 The server ultimately chooses what type to use from the values that are
|
H A D | EVP_PKEY_copy_parameters.pod | 72 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 D | EVP_KDF.pod | 113 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 216 cipher, these parameters set what the algorithm should be. 246 The length must never exceed what can be given with a B<size_t>. 259 The memory size must never exceed what can be given with a B<size_t>.
|
H A D | OSSL_STORE_expect.pod | 8 - Specify what object type is expected 22 OSSL_STORE_expect() helps applications filter what OSSL_STORE_load() returns
|
H A D | OSSL_ENCODER_CTX_new_for_pkey.pod | 44 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 D | OSSL_DECODER_CTX.pod | 87 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. 143 the input is expected to have. This may be used to determines what decoder
|
H A D | EVP_PKEY_is_a.pod | 72 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 D | X509_LOOKUP.pod | 112 I<type> indicates what type of object is expected. 122 I<type> indicates what type of object is expected. 204 Otherwise, it returns what the control function in the 222 Otherwise, they return what the corresponding function in the
|
H A D | EVP_MAC.pod | 161 To figure out what the output length will be and allocate space for it 171 The set of parameters given with I<params> determine exactly what 178 The set of parameters given with I<params> determine exactly what 185 The set of parameters given with I<params> determine exactly what 190 Also, what happens when a needed parameter isn't passed down is 303 digest, these parameters set what the algorithm should be. 317 what can be given with a B<size_t>. 353 after EVP_MAC_final() has been called cannot reset its cipher state to what it
|
H A D | BIO_ADDRINFO.pod | 46 uses B<lookup_type> to determine what the default address should 48 determine what protocol family, socket type and protocol should be used for
|
/openssl/doc/internal/man3/ |
H A D | ossl_algorithm_do_all.pod | 41 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 D | c_rehash.in | 236 my $what = $is_cert ? 'certificate' : 'CRL'; 237 print STDERR "WARNING: Skipping duplicate $what $fname\n";
|
/openssl/doc/man1/ |
H A D | openssl-list.pod.in | 66 The options below where verbosity applies say a bit more about what that means. 141 information on what parameters each implementation supports. 160 information on what parameters each implementation supports. 169 information on what parameters each implementation supports. 241 of what type of parameter it takes, if any.
|
/openssl/apps/lib/ |
H A D | apps_ui.c | 152 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/man7/ |
H A D | provider-decoder.pod | 119 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 D | provider-encoder.pod | 136 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 D | certificates.txt | 6 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/test/recipes/30-test_evp_data/ |
H A D | evpmac_sm3.txt | 36 Input = "what do ya want for nothing?"
|
/openssl/dev/release-aux/ |
H A D | README.md | 21 that instructs it what update to do.
|
/openssl/Configurations/ |
H A D | common0.tmpl | 7 # need to extrapolate exactly what we need to generate. The way to do
|
H A D | INTERNALS.Configure | 10 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
|