aboutsummaryrefslogtreecommitdiffstats
path: root/crypto/crypto.h
Commit message (Collapse)AuthorAgeFilesLines
* Eliminate "statement with no effect" warning when OPENSSL_assert macroAndy Polyakov2005-05-081-1/+1
| | | | is used with constant assertion.
* Replace overwritten lines before error codes.Dr. Stephen Henson2005-04-121-0/+3
|
* Rebuild error codes.Dr. Stephen Henson2005-04-121-3/+0
|
* OPENSSL_ia32cap final touches. Note that OPENSSL_ia32cap is no longer aAndy Polyakov2004-08-291-0/+3
| | | | | symbol, but a macro expanded as (*(OPENSSL_ia32cap_loc())). The latter is the only one to be exported to application.
* Reduce dependencies on crypto.h by moving the opaque definition ofGeoff Thorpe2004-05-171-12/+17
| | | | CRYPTO_EX_DATA and the new/free/dup callback prototypes to ossl_typ.h.
* Setting the ex_data index is unsafe in a threaded environment, soRichard Levitte2003-10-061-1/+2
| | | | let's wrap it with a lock.
* Define the OPENSSL_ITEM structure.Richard Levitte2003-05-011-1/+13
|
* Make sure we get the definition of OPENSSL_NO_FP_API.Richard Levitte2003-03-201-0/+2
|
* new lock for EC_PRE_COMP structuresBodo Möller2003-02-121-2/+3
| | | | Submitted by: Nils Larsch
* Implement a stateful variant if the ZLIB compression method. The oldRichard Levitte2002-12-081-0/+1
| | | | stateless variant is kept, but isn't used anywhere.
* Windows CE updates, contributed by Steven Reddie <smr@essemer.com.au>Richard Levitte2002-12-031-3/+0
|
* Add OPENSSL_cleanse() to help cleanse memory and avoid certain compilerRichard Levitte2002-11-271-0/+2
| | | | | and linker optimizations. PR: 343
* WinCE patchesRichard Levitte2002-11-151-0/+3
|
* Merge from 0.9.7-stable.Richard Levitte2002-11-131-0/+4
|
* Security fixes brought forward from 0.9.7.Ben Laurie2002-11-131-1/+4
|
* clean up new code for NIST primesBodo Möller2002-10-281-1/+55
| | | | create new lock CRYPTO_LOCK_BN to avoid race condition
* really fix race conditionBodo Möller2002-09-231-25/+26
| | | | PR: 262
* Add ECDH support.Bodo Möller2002-08-091-1/+8
| | | | | | | | | | | | | Additional changes: - use EC_GROUP_get_degree() in apps/req.c - add ECDSA and ECDH to apps/speed.c - adds support for EC curves over binary fields to ECDSA - new function EC_KEY_up_ref() in crypto/ec/ec_key.c - reorganize crypto/ecdsa/ecdsatest.c - add engine support for ECDH - fix a few bugs in ECDSA engine support Submitted by: Douglas Stebila <douglas.stebila@sun.com>
* new locksBodo Möller2002-02-131-1/+4
|
* Fix apps/openssl.c and ssl/ssltest.c so that they useBodo Möller2001-09-101-5/+8
| | | | | | | | | | | | | 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).
* Totally get rid of CRYPTO_LOCK_ERR_HASH.Bodo Möller2001-09-061-3/+2
| | | | | | | | | 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.
* delete redundant ERR_load_CRYPTO_strings() prototypeBodo Möller2001-09-041-1/+0
|
* First step in fixing "ex_data" support. Warning: big commit log ...Geoff Thorpe2001-09-011-8/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* md_rand.c thread safetyBodo Möller2001-07-251-13/+14
|
* Add a general user interface API. This is designed to replace thingsRichard Levitte2001-05-061-1/+2
| | | | | | | 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.
* One indirection level too little compared to theRichard Levitte2001-02-221-1/+1
| | | | pre-CRYPTO_MEM_LEAK_CB time.
* Make all configuration macros available for application by makingRichard Levitte2001-02-191-3/+3
| | | | | | | | | | | | 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.
* New function OPENSSL_issetugid(). Needs more work.Ulf Möller2001-02-141-0/+2
|
* Add SSLEAY_DIR argument code for SSLeay_version.Bodo Möller2001-01-101-0/+1
| | | | Add '-d' option for 'openssl version' (included in '-a').
* Change prototypes for new CRYPTO_..._mem_ex_functions functions soBodo Möller2001-01-101-4/+4
| | | | | that they match the function definitions (namely, remove file/line parameters from free_func).
* As response to a user request to be able to use external memoryRichard Levitte2001-01-101-0/+10
| | | | | | 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.
* Get rid of the function pointer casting in the debugging memory code dueGeoff Thorpe2001-01-091-1/+2
| | | | | to LHASH usage. NB: The callback type used as been suctioned off into crypto.h as CRYPTO_MEM_LEAK_CB to improve clarity.
* Constification of CRYPTO_get_ex_data() needed for the sake ofRichard Levitte2000-11-061-1/+1
| | | | RSA_get_ext_data().
* Merge the engine branch into the main trunk. All conflicts resolved.Richard Levitte2000-10-261-1/+2
| | | | At the same time, add VMS support for Rijndael.
* It's not just VMS that needs some symbols to be hacked. Let'sRichard Levitte2000-09-071-10/+3
| | | | | centralise those hacks in crypto/symhacks.h and use it everywhere it's needed.
* Remove casts that are no longer needed.Richard Levitte2000-08-011-5/+5
|
* Add the missing callback pointer handling functions.Richard Levitte2000-06-191-8/+7
| | | | | | 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...
* Redo the support for dynamic locks. First of all, it was terriblyRichard Levitte2000-06-191-6/+13
| | | | | | 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.
* Add support for dynamically created and destroyed mutexes. This willRichard Levitte2000-06-181-0/+19
| | | | | | | | | 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 :-)).
* Safe stack reorganisation in terms of function casts.Dr. Stephen Henson2000-06-161-31/+0
| | | | | | | | | | | | 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.
* There have been a number of complaints from a number of sources that namesRichard Levitte2000-06-011-7/+8
| | | | | | | | | 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.
* "make update" + stripping the type-specific stack functions out ofGeoff Thorpe2000-06-011-0/+31
| | | | libeay.num and ssleay.num.
* is needed.Ulf Möller2000-06-011-0/+2
|
* #include <stdlib.h> is not needed.Ulf Möller2000-05-311-2/+0
|
* Move Windows seeding functions into a separate file.Bodo Möller2000-05-311-1/+0
| | | | They have nothing to do with the particular PRNG (md_rand.c).
* prototype.Ulf Möller2000-05-151-1/+1
|
* In Message-ID: <003201bfb332$14a07520$0801a8c0@janm.transactionsite.com>,Richard Levitte2000-05-021-6/+14
| | | | | | | | | | | | "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).
* This commit ties the new DSO code (crypto/dso/) into the build for aGeoff Thorpe2000-04-041-1/+2
| | | | | | | | | | | | | | | | | | | | | 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:
* Since a stack with quite long name is declared here, vms_idhacks.h isRichard Levitte2000-02-261-1/+6
| | | | | | 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.
* Make gcc 2.95.2 happy again, even under ``-Wall -Wshadow -Wpointer-arith ↵Ralf S. Engelschall2000-02-111-3/+3
| | | | | | -Wcast-align -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline''.
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-29 18:41:49 +0000