- 01 6月, 2008 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 26 5月, 2008 1 次提交
-
-
由 Ben Laurie 提交于
-
- 28 2月, 2008 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 20 4月, 2004 1 次提交
-
-
由 Geoff Thorpe 提交于
tree. This further reduces header interdependencies, and makes some associated cleanups.
-
- 29 10月, 2003 1 次提交
-
-
由 Geoff Thorpe 提交于
choice but to have to cast away "const" qualifiers from their prototypes. This does not remove constification restrictions from hash/compare callbacks, but allows destructor commands to be run over a tables' elements without bad casts.
-
- 07 9月, 2001 1 次提交
-
-
由 Ben Laurie 提交于
-
- 04 9月, 2001 1 次提交
-
-
由 Bodo Möller 提交于
-
- 03 9月, 2001 2 次提交
-
-
由 Geoff Thorpe 提交于
Henson). Also, reverse a previous change that used an implicit function pointer cast rather than an explicit data pointer cast in the STACK cleanup code.
-
由 Ben Laurie 提交于
-
- 02 9月, 2001 1 次提交
-
-
由 Geoff Thorpe 提交于
Currently, this change merely addresses where ex_data indexes are stored and managed, and thus fixes the thread-safety issues that existed at that level. "Class" code (eg. RSA, DSA, etc) no longer store their own STACKS and per-class index counters - all such data is stored inside ex_data.c. So rather than passing both STACK+counter to index-management ex_data functions, a 'class_index' is instead passed to indicate the class (eg. CRYPTO_EX_INDEX_RSA). New classes can be dynamically registered on-the-fly and this is also thread-safe inside ex_data.c (though whether the caller manages the return value in a thread-safe way is not addressed). This does not change the "get/set" functions on individual "ex_data" structures, and so thread-safety at that level isn't (yet) assured. Likewise, the method of getting and storing per-class indexes has not changed, so locking may still be required at the "caller" end but is nonetheless thread-safe inside "ex_data"'s internal implementation. Typically this occurs when code implements a new method of some kind and stores its own per-class index in a global variable without locking the setting and usage of that variable. If the code in question is likely to be used in multiple threads, locking the setting and use of that index is still up to the code in question. Possible fixes to this are being sketched, but definitely require more major changes to the API itself than this change undertakes. The underlying implementation in ex_data.c has also been modularised so that alternative "ex_data" implementations (that control all access to state) can be plugged in. Eg. a loaded module can have its implementation set to that of the application loaded it - the result being that thread-safety and consistency of "ex_data" classes and indexes can be maintained in the same place rather than the loaded module using its own copy of ex_data support code and state. Due to the centralisation of "state" with this change, cleanup of all "ex_data" state can now be performed properly. Previously all allocation of ex_data state was guaranteed to leak - and MemCheck_off() had been used to avoid it flagging up the memory debugging. A new function has been added to perfrom all this cleanup, CRYPTO_cleanup_all_ex_data(). The "openssl" command(s) have been changed to use this cleanup, as have the relevant test programs. External application code may want to do so too - failure to cleanup will not induce more memory leaking than was the case before, but the memory debugging is not tricked into hiding it any more so it may "appear" where it previously did not.
-
- 18 12月, 2000 1 次提交
-
-
由 Bodo Möller 提交于
-
- 16 12月, 2000 1 次提交
-
-
由 Bodo Möller 提交于
-
- 07 11月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
RSA_get_ext_data().
-
- 16 10月, 2000 1 次提交
-
-
由 Richard Levitte 提交于
-
- 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.
-
- 24 1月, 2000 1 次提交
-
-
由 Dr. Stephen Henson 提交于
Tidy up CRYPTO_EX_DATA structures.
-
- 23 7月, 1999 1 次提交
-
-
由 Ulf Möller 提交于
Still doesn't work (the destructor on BIO and SSL is called immediately after creating the object. Why that??)
-
- 19 5月, 1999 1 次提交
-
-
由 Dr. Stephen Henson 提交于
to minimise the effects on existing code.
-
- 24 4月, 1999 1 次提交
-
-
由 Bodo Möller 提交于
Submitted by: Reviewed by: PR:
-
- 20 4月, 1999 1 次提交
-
-
由 Ulf Möller 提交于
-
- 21 12月, 1998 3 次提交
-
-
由 Ralf S. Engelschall 提交于
-
由 Ralf S. Engelschall 提交于
-
由 Ralf S. Engelschall 提交于
-