summaryrefslogtreecommitdiff
path: root/crypto/cryptlib.c
Commit message (Collapse)AuthorAgeFilesLines
* Add BeOS support.Ulf Möller2006-04-111-0/+2
| | | | | | PR: 1312 Submitted by: Oliver Tappe <zooey@hirschkaefer.de> Reviewed by: Ulf Moeller
* Unify sparcv9 assembler naming and build rules among 32- and 64-bit builds.Andy Polyakov2005-12-161-1/+1
| | | | Engage run-time switch between bn_mul_mont_fpu and bn_mul_mont_int.
* WCE update, mostly typos.Andy Polyakov2005-08-031-2/+2
|
* WCE-specific fix for cryptlib.c.Andy Polyakov2005-08-021-16/+6
|
* Pull up Win64 support from 0.9.8.Andy Polyakov2005-07-051-1/+1
|
* Move _WIN32_WINNT definition from command line to e_os.h. The change isAndy Polyakov2005-05-211-2/+3
| | | | | inspired by VC6 failure report. In addition abstain from taking screen snapshots when running in NT service context.
* Cygwin doesn't expose Win32 [not "officially"].Andy Polyakov2005-05-031-1/+1
|
* Provide a default OPENSSL_ia32cap_loc for non-Intel platforms whereRichard Levitte2005-04-211-0/+2
| | | | | util/libeay.num is important when building shared libraries, like VMS.
* Fix typos.Andy Polyakov2005-04-131-2/+2
|
* Introduce OPENSSL_NONPIC_relocated to denote relocated DLLs.Andy Polyakov2005-04-131-0/+16
|
* Minor cryptlib.c update: compiler warnings in OPENSSL_showfatal andAndy Polyakov2005-04-131-5/+8
| | | | OPENSSL_stderr stub.
* Implement OPENSSL_showfatal and make it Win32 GUI and service awareAndy Polyakov2005-04-071-1/+136
| | | | | [meaning that it will detect in which context application is running and either write message to stderr, post a dialog or log an event].
* Harmonize cygwin/mingw and VC targets.Andy Polyakov2005-04-071-1/+1
|
* linux-x86_64 didn't link after EM64T RC4 tune-up...Andy Polyakov2004-11-231-1/+3
|
* OPENSSL_ia32cap final touches. Note that OPENSSL_ia32cap is no longer aAndy Polyakov2004-08-291-7/+7
| | | | | symbol, but a macro expanded as (*(OPENSSL_ia32cap_loc())). The latter is the only one to be exported to application.
* Cygwin fix-up for shared build.Andy Polyakov2004-08-011-0/+4
|
* DLLEntryPoint is a collective name, not what linker looks for. However,Andy Polyakov2004-08-011-5/+2
| | | | | | | if we explicitly intruct the linker to set entry point, then we become obliged to initialize run-time library. Instead we can pick name run-time will call and such name is DllMain. Note that this applies to both "native" Win32 environment and Cygwin:-)
* This is so to say "damage control" for jumbo "cpuid" patch, seeAndy Polyakov2004-07-261-1/+1
| | | | | | http://cvs.openssl.org/chngview?cn=12493. Now all platform should be operational, while SSE2 code pathes get engaged on ELF platforms only.
* Add framework for yet another assembler module dubbed "cpuid." IdeaAndy Polyakov2004-07-261-0/+33
| | | | | | | | | | | is to have a placeholder to small routines, which can be written only in assembler. In IA-32 case this includes processor capability identification and access to Time-Stamp Counter. As discussed earlier OPENSSL_ia32cap is introduced to control recently added SSE2 code pathes (see docs/crypto/OPENSSL_ia32cap.pod). For the moment the code is operational on ELF platforms only. I haven't checked it yet, but I have all reasons to believe that Windows build should fail to link too. I'll be looking into it shortly...
* (oops) Apologies all, that last header-cleanup commit was from the wrongGeoff Thorpe2004-04-191-3/+0
| | | | | tree. This further reduces header interdependencies, and makes some associated cleanups.
* 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 a STORE lock (the STORE type will be committed later).Richard Levitte2003-05-011-1/+2
|
* new lock for EC_PRE_COMP structuresBodo Möller2003-02-121-2/+3
| | | | Submitted by: Nils Larsch
* In CRYPTO_lock(), check that the application cares about locking (providedRichard Levitte2002-12-111-7/+7
| | | | callbacks) before attempting to lock.
* sk_*_push() returns the number of items on the stack, not the index of theRichard Levitte2002-12-111-3/+13
| | | | | | | pushed item. The index is the number of items - 1. And if a NULL item was found, actually use it. Finally, provide a little bit of safety in CRYPTO_lock() by asserting the a requested dynamic lock really must exist, instead of just being silent about it
* Security fixes brought forward from 0.9.7.Ben Laurie2002-11-131-0/+8
|
* Off-by-one-error corrected.Richard Levitte2002-11-041-1/+1
| | | | PR: 235
* 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-1/+2
| | | | PR: 262
* Add ECDH support.Bodo Möller2002-08-091-1/+7
| | | | | | | | | | | | | 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>
* get rid of OpenSSLDieBodo Möller2002-08-021-8/+0
|
* OpenSSL Security Advisory [30 July 2002]Lutz Jänicke2002-07-301-0/+8
| | | | | | | Changes marked "(CHATS)" were sponsored by the Defense Advanced Research Projects Agency (DARPA) and Air Force Research Laboratory, Air Force Materiel Command, USAF, under agreement number F30602-01-2-0537.
* new locksBodo Möller2002-02-131-1/+3
|
* This looks to have been a typo.Geoff Thorpe2001-11-241-1/+1
|
* fix submitted by Andy Schneider <andy.schneider@bjss.co.uk>Bodo Möller2001-11-231-0/+3
| | | | (in main branch, hn_ncipher.c is already correct)
* 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.
* First step in fixing "ex_data" support. Warning: big commit log ...Geoff Thorpe2001-09-011-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-1/+2
|
* Don't set pointer if add_lock_callback used.Dr. Stephen Henson2001-06-191-1/+0
|
* Stop mishandling the type number in dynlock lockingRichard Levitte2001-06-011-3/+2
|
* Don't decrement the reference counter twice when destroying dynamicRichard Levitte2001-05-311-2/+2
| | | | links.
* 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.
* Use new-style system-id macros everywhere possible. I hope I haven'tRichard Levitte2001-02-201-5/+5
| | | | | | | missed any. This compiles and runs on Linux, and external applications have no problems with it. The definite test will be to build this on VMS.
* Locking issues.Bodo Möller2000-12-151-1/+1
|
* 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.
* Handle ASN1_SET_OF and PKCS12_STACK_OF using functionDr. Stephen Henson2000-06-201-3/+3
| | | | casts in the same way as STACK_OF.
* Add the missing callback pointer handling functions.Richard Levitte2000-06-191-13/+42
| | | | | | 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...
* Add OPENSSL_free at the end of CRYPTO_destroy_dynlockid.Bodo Möller2000-06-191-0/+3
|
* Redo the support for dynamic locks. First of all, it was terriblyRichard Levitte2000-06-191-59/+85
| | | | | | 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-5/+134
| | | | | | | | | 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 :-)).
View Lorry Controller Status