Lines Matching refs:not
17 supplies various additional supporting APIs that are not directly cryptography
31 Applications may be written that only use C<libcrypto> capabilities and do not
69 If an application does not explicitly create a library context then the
117 time. However most OpenSSL I<data structures> are not thread-safe. For example
119 would not be thread safe to call BIO_write() from one thread while calling
123 There are exceptions to these rules. A small number of functions are not thread
135 function has been successful or not. It is considered best practice to always
146 small number of functions that do not conform to the above conventions (e.g.
154 failure (e.g. for debugging or logging purposes). Many (but not all) functions
204 Some encoding and decoding algorithm implementations are not FIPS algorithm
225 provider does not support the encoding or decoding of keys.
249 all API calls have correctly passed the created library context and are not
283 to the I<crl> object. Therefore, after calling this function I<rev> should not
286 In the B<1> version the ownership of the object is not passed to or retained by
326 Licensed under the Apache License 2.0 (the "License"). You may not use