- 07 5月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
like des_read_password and friends (backward compatibility functions using this new API are provided). The purpose is to remove prompting functions from the DES code section as well as provide for prompting through dialog boxes in a window system and the like.
-
- 22 2月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
pre-CRYPTO_MEM_LEAK_CB time.
-
- 20 2月, 2001 1 次提交
-
-
由 Richard Levitte 提交于
sure they are available in opensslconf.h, by giving them names starting with "OPENSSL_" to avoid conflicts with other packages and by making sure e_os2.h will cover all platform-specific cases together with opensslconf.h. I've checked fairly well that nothing breaks with this (apart from external software that will adapt if they have used something like NO_KRB5), but I can't guarantee it completely, so a review of this change would be a good thing.
-
- 14 2月, 2001 1 次提交
-
-
由 Ulf Möller 提交于
-
- 10 1月, 2001 3 次提交
-
-
由 Bodo Möller 提交于
Add '-d' option for 'openssl version' (included in '-a').
-
由 Bodo Möller 提交于
that they match the function definitions (namely, remove file/line parameters from free_func).
-
由 Richard Levitte 提交于
handling routines that need file name and line number information, I've added a call level to our memory handling routines to allow that kind of hooking.
-
- 09 1月, 2001 1 次提交
-
-
由 Geoff Thorpe 提交于
to LHASH usage. NB: The callback type used as been suctioned off into crypto.h as CRYPTO_MEM_LEAK_CB to improve clarity.
-
- 07 11月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
RSA_get_ext_data().
-
- 27 10月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
At the same time, add VMS support for Rijndael.
-
- 07 9月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
centralise those hacks in crypto/symhacks.h and use it everywhere it's needed.
-
- 01 8月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
-
- 20 6月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
Also, make sure empty slots of the dynamic lock stack are used. Actually, I'm not really sure this is the right thing to do, and may remove it, with an endlessly growing stack as result...
-
- 19 6月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
insecure, so a static lock is added to isolate the sensitive parts. Also, to avoid one thread freeing a lock that is used by another, a reference counter is added.
-
- 18 6月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
be needed in some ENGINE code, and might serve elsewhere as well. Note that it's implemented in such a way that the locking itself is done through the same CRYPTO_lock function as the static locks. WARNING: This is currently experimental and untested code (it will get tested soon, though :-)).
-
- 17 6月, 2000 1 次提交
-
-
由 Dr. Stephen Henson 提交于
After some messing around this seems to work but needs a few more tests. Working out the syntax for sk_set_cmp_func() (cast it to a function that itself returns a function pointer) was painful :-( Needs some testing to see what other compilers think of this syntax. Also needs similar stuff for ASN1_SET_OF etc etc.
-
- 02 6月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
like Malloc, Realloc and especially Free conflict with already existing names on some operating systems or other packages. That is reason enough to change the names of the OpenSSL memory allocation macros to something that has a better chance of being unique, like prepending them with OPENSSL_. This change includes all the name changes needed throughout all C files.
-
- 01 6月, 2000 3 次提交
-
-
由 Geoff Thorpe 提交于
libeay.num and ssleay.num.
-
由 Ulf Möller 提交于
-
由 Ulf Möller 提交于
-
- 31 5月, 2000 1 次提交
-
-
由 Bodo Möller 提交于
They have nothing to do with the particular PRNG (md_rand.c).
-
- 16 5月, 2000 1 次提交
-
-
由 Ulf Möller 提交于
-
- 02 5月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
"Jan Mikkelsen" <janm@transactionsite.com> correctly states that the OpenSSL header files have #include's and extern "C"'s in an incorrect order. Thusly fixed. Also, make the memory debugging routines defined and declared with prototypes, and use void* instead of char* for memory blobs. And last of all, redo the ugly callback construct for elegance and better definition (with prototypes).
-
- 05 4月, 2000 1 次提交
-
-
由 Geoff Thorpe 提交于
variety of platforms. A few are missing, and they will be added in eventually, but as this is new stuff, it was better to not break lots of platforms in one go that we can't easily test. The changes to "Configure" should illustrate how to add support to other systems if you feel like having a go. NB: I'll add something shortly to allow you to add "dlfcn.h" support on those platforms that don't have (or need) a dlfcn.h header file. (The symbol for Configure will probably by "dlfcn_no_h"). Thanks to Richard Levitte, who is responsible for the dso_dl.c support, understanding the trickier aspects of the build process, and giving great feedback on everything else. [Don't use this stuff if you're easily offended by changes to the interface or behaviour - it's still work in progress.] PR:
-
- 26 2月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
also needed to get around C compilers on VMS that set the symbol limit to 31 characters. Bot the macros VMS and __VMS are checked, since there's no real way to know if e_os.h has been included yet.
-
- 11 2月, 2000 1 次提交
-
-
由 Ralf S. Engelschall 提交于
-Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline''.
-
- 31 1月, 2000 1 次提交
-
-
由 Ulf Möller 提交于
eliminate some of the -Wcast-qual warnings (debug-ben-strict target)
-
- 24 1月, 2000 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Tidy up CRYPTO_EX_DATA structures.
-
- 07 1月, 2000 1 次提交
-
-
由 Bodo Möller 提交于
Submitted by: Reviewed by: PR:
-
- 03 1月, 2000 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 18 12月, 1999 5 次提交
-
-
由 Bodo Möller 提交于
CRYPTO_add_info => CRYPTO_push_info CRYPTO_remove_info => CRYPTO_pop_info in the hope that these names are more descriptive; and "make update".
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
(and that malloc can be called with an int argument). - Use proper prototypes (with argument list) for various function pointers, avoid casts (however there are still many such cases left in these files). - Avoid collissions in app_info_cmp if sizeof int != sizeof long. - Use CRYPTO_LOCK_MALLOC in mem_dbg.c.
-
由 Richard Levitte 提交于
- Made CRYPTO_MDEBUG even less used in crypto.h, giving MemCheck_start() and MemCheck_stop() only one possible definition. - Made the values of the debug function pointers in mem.c dependent on the existence of the CRYPTO_MDEBUG macro, and made the rest of the code understand the NULL case. That's it. With this code, the old behvior of the debug functionality is restored, but you can still opt to have it on, even when the library wasn't compiled with a defined CRYPTO_MDEBUG.
-
由 Richard Levitte 提交于
- Moved the handling of compile-time defaults from crypto.h to mem_dbg.c, since it doesn't make sense for the library users to try to affect this without recompiling libcrypto. - Made sure V_CRYPTO_MDEBUG_TIME and V_CRYPTO_MDEBUG_THREAD had clear and constant definitions. - Aesthetic correction.
-
- 17 12月, 1999 1 次提交
-
-
由 Richard Levitte 提交于
With this change, the following is provided and present at all times (meaning CRYPTO_MDEBUG is no longer required to get this functionality): - hooks to provide your own allocation and deallocation routines. They have to have the same interface as malloc(), realloc() and free(). They are registered by calling CRYPTO_set_mem_functions() with the function pointers. - hooks to provide your own memory debugging routines. The have to have the same interface as as the CRYPTO_dbg_*() routines. They are registered by calling CRYPTO_set_mem_debug_functions() with the function pointers. I moved everything that was already built into OpenSSL and did memory debugging to a separate file (mem_dbg.c), to make it clear what is what. With this, the relevance of the CRYPTO_MDEBUG has changed. The only thing in crypto/crypto.h that it affects is the definition of the MemCheck_start and MemCheck_stop macros.
-
- 12 11月, 1999 1 次提交
-
-
由 Richard Levitte 提交于
1. Added code to the memory leak detecting code to give the user the possibility to add information, thereby forming a traceback. 2. Make the memory leak detecting code multithread-safe. The idea is that we're actually dealing with two separate critical sections, one containing the hash tables with the information, the other containing the current memory checking mode. Those should not be handled with the same lock, especially since their handling overlap. Hence, the added second lock.
-
- 24 8月, 1999 1 次提交
-
-
由 Dr. Stephen Henson 提交于
DSA_METHOD to make it more consistent with RSA_METHOD.
-
- 19 7月, 1999 2 次提交
-
-
由 Bodo Möller 提交于
-
由 Bodo Möller 提交于
and make it the default for some debugging configurations.
-