summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/engine/eng_all.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Set OPENSSL_NO_ENGINE, remove engine codetb2023-07-281-88/+0
| | | | | | | | | | ENGINE was special. It's horrible code even by the low standards of this library. Some ports may now try to use the stubs which will fail, but the fallout from this should be minimal. Of course there are various language bindings that expose the ENGINE API. OpenSSL 3 disabling ENGINE by default will likely help fixing this at some point. ok jsing
* Bring in compatibility for OpenSSL 1.1 style init functions.beck2018-03-171-5/+15
| | | | | | | | | This adds OPENSSL_init_crypto and OPENSSL_init_ssl, as well thread safety modifications for the existing LibreSSL init functions. The initialization routines are called automatically by the normal entry points into the library, as in newer OpenSSL ok jsing@, nits by tb@ and deraadt@
* Remove OpenSSL engine RSAX.doug2015-07-191-4/+1
| | | | | | | | | OpenSSL stopped building it last year and removed it this year. Based on OpenSSL commit c436e05bdc7f49985a750df64122c960240b3ae1. Also cranked major version in libcrypto, libssl and libtls. "fine with me" bcook@ miod@
* Disable ENGINE_load_dynamic (dynamic engine support).bcook2015-06-191-2/+1
| | | | | | | We do not build, test or ship any dynamic engines, so we can remove the dynamic engine loader as well. This leaves a stub initialization function in its place. ok beck@, reyk@, miod@
* Delete a lot of #if 0 code in libressl.doug2015-02-071-8/+1
| | | | | | | | | | | | | | | | | | | | | | | | | There are a few instances where #if 1 is removed but the code remains. Based on the following OpenSSL commits. Some of the commits weren't strictly deletions so they are going to be split up into separate commits. 6f91b017bbb7140f816721141ac156d1b828a6b3 3d47c1d331fdc7574d2275cda1a630ccdb624b08 dfb56425b68314b2b57e17c82c1df42e7a015132 c8fa2356a00cbaada8963f739e5570298311a060 f16a64d11f55c01f56baa62ebf1dec7f8fe718cb 9ccc00ef6ea65567622e40c49aca43f2c6d79cdb 02a938c953b3e1ced71d9a832de1618f907eb96d 75d0ebef2aef7a2c77b27575b8da898e22f3ccd5 d6fbb194095312f4722c81c9362dbd0de66cb656 6f1a93ad111c7dfe36a09a976c4c009079b19ea1 1a5adcfb5edfe23908b350f8757df405b0f5f71f 8de24b792743d11e1d5a0dcd336a49368750c577 a2b18e657ea1a932d125154f4e13ab2258796d90 8e964419603d2478dfb391c66e7ccb2dcc9776b4 32dfde107636ac9bc62a5b3233fe2a54dbc27008 input + ok jsing@, miod@, tedu@
* Explicitly include <openssl/opensslconf.h> in every file that referencesjsing2014-07-101-1/+3
| | | | | | | | | an OPENSSL_NO_* define. This avoids relying on something else pulling it in for us, plus it fixes several cases where the #ifndef OPENSSL_NO_XYZ is never going to do anything, since OPENSSL_NO_XYZ will never defined, due to the fact that opensslconf.h has not been included. This also includes some miscellaneous sorting/tidying of headers.
* tags as requested by miod and teduderaadt2014-06-121-1/+1
|
* c-file-style hints, begone; ok beckderaadt2014-06-111-1/+1
|
* Abandon the auto-ENGINE /dev/crypto interface. VIA 3des cbc receivesderaadt2014-06-101-17/+1
| | | | | | | | | | | | | collateral damage. The syncronous nature of this mechanism has hampered performance for symmetric crypto relative to brute-force cpu. The assymetric crypto support never really materialized in drivers. So abandon the complexity. ok tedu beck mikeb some disagrement from djm but if he wants to test /dev/crypto ciphers he should do it without this this gigantic API in the way
* KNF.jsing2014-06-101-6/+10
|
* A few months back there was a big community fuss regarding direct-usederaadt2014-06-021-3/+0
| | | | | | | | | | | | of the intel RDRAND instruction. Consensus was RDRAND should probably only be used as an additional source of entropy in a mixer. Guess which library bends over backwards to provide easy access to RDRAND? Yep. Guess which applications are using this support? Not even one... but still, this is being placed as a trap for someone. Send this support straight to the abyss. ok kettenis
* Remove the GOST engine: It is not compiled or used and depends on thereyk2014-04-151-3/+0
| | | | | | | | "dynamic engine" feature that is not enabled in our build. People who need it can still pull it out of the Attic; if it is to have a Russian engine just because it's a Russian engine. OK deraadt@ beck@
* Remove the GMP engine: It was an experimental engine using libgmp asreyk2014-04-141-3/+0
| | | | | | | an alternative backend for BIGNUM calculations. It is PoC code that is not enabled in OpenSSL and probably not used by anymore. ok deraadt@
* Remove the CAPI engine: It is a backend for the Windows CryptoAPI andreyk2014-04-141-3/+0
| | | | | | could be maintained in an external package. "it should probably go" beck@
* Remove the nuron engine. The static engine is not standalone and thereyk2014-04-141-3/+0
| | | | FPGA-based device is long obsolete.
* Remove the nCipher CHIL engine. It is not standalone and depends onreyk2014-04-141-3/+0
| | | | external libraries that aren't covered by the same license.
* Remove the AEP engine: it is not standalone and doesn't seem to bereyk2014-04-131-3/+0
| | | | | | | | | relevant anymore. OpenSSL should have a better way to include 3rd party engines: either completely and free or external. But including a wrapper for a non-free wrapper in the code base does not make much sense and could also be provided by the vendor. ok deraadt@
* Remove the Atalla engine: It is not standalone and depends on externalreyk2014-04-131-3/+0
| | | | | | | | | non-free libraries. OpenSSL should have a better way to include 3rd party engines: either completely free or external. But including a wrapper for a non-free wrapper in the code base does not make much sense and could also be provided by the vendor. ok deraadt@
* Remove the cswift engine: it is not standalone and we don't have thereyk2014-04-131-3/+0
| | | | | | | | | | | | | hardware. The vendor_defns/cswift.h does not specify a copyright and theoretically defaults to the OpenSSL license, but it also mentions that it includes parts that have been "clipped" from CryptoSwift's proprietary headers. This file should better include an explicit copyright statement or mention OpenSSL's library instead of the ambiguous "Attribution notice". ok deraadt@
* Remove the "sureware" engine:reyk2014-04-131-3/+0
| | | | | | | | | | | | The vendor_defns/sureware.h file by Baltimore Technologies Ltd. has a copyright that does not grant rights! Vendor files should either include a compatible license in the copyright statement or use OpenSSL's defaults, but adding a copyright statement without any terms is not acceptable. It should not have been included in the first place. ok deraadt@
* Remove the Broadcom ubsec engine:reyk2014-04-131-3/+0
| | | | | | | | | | | | | The vendor_defns/hw_ubsec.h file has a copyright that does not grant rights! Vendor files should either include a compatible license in the copyright statement or use OpenSSL's defaults, but adding a copyright statement without any terms is not acceptable. It should not have been included in the first place. (The ubsec(4) kernel driver is not affected by this change) ok deraadt@
* Remove the IBM 4758 engine: we don't have this hardware and it is anreyk2014-04-131-3/+0
| | | | | | old PCI accelerator that was EOL'ed in 2005. ok deraadt@
* Merge conflicts; remove MacOS, Netware, OS/2, VMS and Windows build machinery.miod2014-04-131-1/+0
|
* resolve conflictsdjm2012-10-131-3/+8
|
* resolve conflicts, fix local changesdjm2010-10-011-9/+10
|
* AES-NI engine support for OpenSSL.thib2010-07-011-0/+5
| | | | | | | | | | This is code mostly picked up from upstream OpenSSL, or to be more exact a diff from David Woodhouse <dwmw2 at infradead dot org>. Remember to make includes before doing a build! no objections from djm@ OK deraadt@, reyk@ (AES is about 4.25x faster on his x201 now)
* update to openssl-0.9.8i; tested by several, especially krw@djm2009-01-051-0/+3
|
* resolve conflictsdjm2008-09-061-11/+20
|
* merge 0.9.7b with local changes; crank majors for libssl/libcryptomarkus2003-05-121-12/+6
|
* merge with 0.9.7-beta1markus2002-09-051-2/+3
|
* OpenSSL 0.9.7 stable 2002 05 08 mergebeck2002-05-151-0/+118