Searched refs:results (Results 26 – 50 of 71) sorted by relevance
123
107 results. They should no longer be used and are therefore deprecated.
111 unexpected results.
61 The functions return their respective main results directly, while there are62 also accessor functions for retrieving various results and status information
49 B<UI_STRING> objects as well as adding results to some of them.
75 finalize the B<PKCS7> structure will give unpredictable results.
66 B<BIO_ADDR>. The possible non-error results are one of the
119 may lead to unexpected results if the same CA certificate is available
104 If processing a received protocol message results in an error,
91 results.
425 on X.509v3 extensions, etc., and losing it can lead to wrong validation results.
155 SSL_get_servername() historically provided some unexpected results in certain
64 results.
95 is specified an error results.
35 and does not influence the normal data stream (unless its contents results
155 unexpected results: for example no current filter BIOs implement
88 several possible related results. This also includes chaining decoders, so
69 any successful call to BIO_read() results in the peer address used for any
308 # "Known-answer and Monte Carlo test results, as of round 3
15 # AES_CBC results for aligned block lengths. (Result should be the same as 32 byte CTS1 & CTS2)
53 [A report is available](REPORT.md) on the results of the DDD process following
117 This is useful for L<provider-storemgmt(7)> when a URI load results in new
84 other pass phrase encoding may give undefined results.
163 environment variable value that must be used to recreate the results), e.g.
159 connection setup. This results in the coverage of the fuzzing corpus changing
603 gdb < <(echo -e "file ./libcrypto.so.3\nquit") > ./results604 grep -q "Reading symbols from.*libcrypto\.so\.3\.debug" results
Completed in 50 milliseconds