- 26 9月, 2001 1 次提交
-
-
由 Geoff Thorpe 提交于
digest support, are on their way. Rather than having gigantic commit log messages and/or CHANGES entries, this change to the README will serve as an outline of what it all is and how it all works.
-
- 25 9月, 2001 1 次提交
-
-
由 Dr. Stephen Henson 提交于
16.
-
- 24 9月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
Noticed by Thomas Klausner <wiz@danbala.ifoer.tuwien.ac.at>.
-
- 20 9月, 2001 1 次提交
-
-
由 Bodo Möller 提交于
-
- 15 9月, 2001 4 次提交
-
-
由 Geoff Thorpe 提交于
recently. So comments including file names have been fixed, and copyright notices brought up to "2001" at the same time.
-
由 Geoff Thorpe 提交于
and DH all conditional upon OPENSSL_NO_RSA.
-
由 Geoff Thorpe 提交于
tested previously.
-
由 Geoff Thorpe 提交于
fix a typo and add cleanup operations. This also switches on memory leak checking (which is how the rest was found).
-
- 13 9月, 2001 1 次提交
-
-
由 Bodo Möller 提交于
-
- 12 9月, 2001 3 次提交
-
-
由 Geoff Thorpe 提交于
in "types.h" so that very few headers will need to include engine.h, generally only C files using API functions will need it (reducing the header dependencies quite a lot).
-
由 Geoff Thorpe 提交于
-
由 Dr. Stephen Henson 提交于
Fix X509V3 macro so they compile.
-
- 11 9月, 2001 7 次提交
-
-
由 Geoff Thorpe 提交于
-
由 Geoff Thorpe 提交于
-
由 Ulf Möller 提交于
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
-
- 10 9月, 2001 5 次提交
-
-
由 Bodo Möller 提交于
distinction (which does not work well because if CRYPTO_MDEBUG is defined at library compile time, it is not necessarily defined at application compile time; and memory debugging now can be reconfigured at run-time anyway). To get the intended semantics, we could just use the EVP_DigestInit_dbg unconditionally (which uses the caller's __FILE__ and __LINE__ for memory leak debugging), but this would make memory debugging inconsistent. Instead, callers can use CRYPTO_push_info() to track down memory leaks.
-
由 Bodo Möller 提交于
distinction (which does not work well because if CRYPTO_MDEBUG is defined at library compile time, it is not necessarily defined at application compile time; and memory debugging now can be reconfigured at run-time anyway). To get the intended semantics, we could just use the EVP_DigestInit_dbg unconditionally (which uses the caller's __FILE__ and __LINE__ for memory leak debugging), but this would make memory debugging inconsistent. Instead, callers can use CRYPTO_push_info() to track down memory leaks. Also fix indentation, and add OpenSSL copyright.
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
CRYPTO_set_mem_debug_options() instead of CRYPTO_dbg_set_options(), which is the default implementation of the former and should usually not be directly used by applications (at least if we assume that the options accepted by the default implementation will also be meaningful to any other implementations). Also fix apps/openssl.c and ssl/ssltest such that environment variable setting 'OPENSSL_DEBUG_MEMORY=off' actively disables the compiled-in library defaults (i.e. such that CRYPTO_MDEBUG is ignored in this case).
-
- 08 9月, 2001 2 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Bodo Möller 提交于
<openssl/evp.h> is now used (MD_DIGEST_LENGTH definitions!). No need to include such headers directly in md_rand.c.
-
- 07 9月, 2001 8 次提交
-
-
由 Ben Laurie 提交于
-
由 Ben Laurie 提交于
-
由 Ben Laurie 提交于
-
由 Ben Laurie 提交于
-
由 Ulf Möller 提交于
-
由 Ulf Möller 提交于
-
由 Ulf Möller 提交于
-
由 Ulf Möller 提交于
-
- 06 9月, 2001 6 次提交
-
-
由 Bodo Möller 提交于
(Some platforms need _XOPEN_SOURCE and _XOPEN_SOURCE_EXTENDED to get the declaration, but on other platforms _XOPEN_SOURCE disables the strdup declaration in <string.h>.)
-
由 Bodo Möller 提交于
In err.c, flags int_error_hash_set and int_thread_hash_set appear superfluous since we can just as well initialize int_error_hash and int_thread_hash to NULL. Change some of the err.c formatting to conform with the rest of OpenSSL.
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
-
由 Geoff Thorpe 提交于
error strings - the destroy handler functions unload the error strings so any pending error state referring to them will not attempt to reference them after the ENGINE has been destroyed.
-
由 Geoff Thorpe 提交于
being enabled or disabled (respectively) for operation. Additionally, each ENGINE has a constructor function where it can do more 'structural' level intialisations such as loading error strings, creating "ex_data" indices, etc. This change introduces a handler function that gives an ENGINE a corresponding opportunity to cleanup when the ENGINE is being destroyed. It also adds the "get/set" API functions that control this "destroy" handler function in an ENGINE.
-