summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/crypto/Makefile (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove the libcrypto/crypto directorybeck2016-09-031-430/+0
|
* Stop supporing "legcay" time formats that OpenSSL supports. Rewrite thebeck2015-10-191-2/+2
| | | | | | utctime and gentime wrappers accordingly. Along with some other cleanup. this also removes the need for timegm. ok bcook@ sthen@ jsing@
* Flense the greasy black guts of unreadble string parsing code out of three areasbeck2015-10-021-1/+2
| | | | | | | | | in asn1 and x509 code, all dealing with an ASN1_TIME. This brings the parsing together in one function that converts into a struct tm. While we are at it this also brings us into conformance with RFC 5280 for times allowed in an X509 cert, as OpenSSL is very liberal with what it allows. input and fixes from deraadt@ jsing@ guethther@ and others. ok krw@, guenther@, jsing@
* Temporarily revive MD4 for MS CHAP support.doug2015-09-141-2/+7
|
* Remove MD4 support from LibreSSL.doug2015-09-131-7/+2
| | | | | | | | MD4 should have been removed a long time ago. Also, RFC 6150 moved it to historic in 2011. Rides the major crank from removing SHA-0. Discussed with many including beck@, millert@, djm@, sthen@ ok jsing@, input + ok bcook@
* Remove SHA-0 support.doug2015-09-131-3/+3
| | | | | | | SHA-0 was withdrawn shortly after publication 20 years ago and replaced with SHA-1. This will require a major crank. ok bcook@, jsing@
* Merge ech_ossl.c into ech_key.c - not much point having one file with ajsing2015-09-131-2/+2
| | | | | | four line function and a tonne of license text. ok beck@
* Nuke openssl/e_os2.h, since nothing should be using it.jsing2015-09-131-2/+1
| | | | ok deraadt@ "hurray! finally!" miod@ "Yay!" sthen@
* Remove OpenSSL engine RSAX.doug2015-07-191-2/+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@
* Fix pointer to unsigned long conversion.doug2015-06-271-2/+2
| | | | | | | bcook@ notes that this check really only impacted 64-bit Windows. Also, changed the check to be unsigned for consistency. ok bcook@
* Remove obsolete MDC-2DES from libcrypto.doug2015-06-201-7/+2
| | | | ok deraadt@ jsing@ miod@
* Send OPENSSL_issetugid() straight to hell, no final cigarette.deraadt2015-04-111-2/+2
| | | | | | | | | | | | | | | | | | | The issetugid() API is supposed to make a strong promise where "0 means it is safe to look at the environment". Way back in the past someone on the OpenSSL team responded to the environment access danger by creating a wrapper called OPENSSL_issetugid, and went to use it a number of places. However, by default on systems lacking true issetugid(), OPENSSL_issetugid returns 0. 0 indicating safely. False safety. Which means OPENSSL_issetugid() fails to make any sort of promise about safety, in fact it is just the opposite. Can you believe the OpenSSL team? This nastiness was noticed over the years, however noone could gain traction and get it fixed in OpenSSL. Also see a paragraph about this in http://www.tedunangst.com/flak/post/worst-common-denominator-programming ok jsing
* unifdef OPENSSL_NO_RFC3779 - this is currently disabled and unlikely tojsing2015-02-101-2/+1
| | | | | | be enabled, mostly since people use SANs instead. ok beck@ guenther@
* Remove RC5 code - this is not currently enabled and is not likely to everjsing2015-02-101-8/+2
| | | | | | | | be enabled. Removes one symbol from libcrypto, however there is no ABI change. ok beck@ miod@ tedu@
* Remove crypto/store - part of which is "currently highly experimental".jsing2015-02-101-6/+1
| | | | | | | This code is not compiled in and OPENSSL_NO_STORE is already defined in opensslfeatures.h. No symbol removal for libcrypto. ok beck@
* Combine c_allc.c and c_alld.c into c_all.c - there is not much point havingjsing2015-02-071-2/+2
| | | | | | | this split across files, especially when two of them have less code than license text. ok bcook@ beck@ doug@ miod@
* Add X509_STORE_load_mem() to load certificates from a memory bufferreyk2015-01-221-2/+2
| | | | | | | | | | | instead of disk. OpenSSL didn't provide a built-in API from loading certificates in a chroot'ed process that doesn't have direct access to the files. X509_STORE_load_mem() provides a new backend that will be used by libssl and libtls to implement such privsep-friendly functionality. Adopted for LibreSSL based on older code from relayd (by pyr@ and myself) With feedback and OK bluhm@
* Move Windows OS-specific functions to make porting easier.bcook2014-12-031-5/+5
| | | | | | | | | Several functions that need to be redefined for a Windows port are right in the middle of other code that is relatively portable. This patch isolates the functions that need Windows-specific implementations so they can be built conditionally in the portable tree. ok jsing@ deraadt@
* Oops, make sure camellia is compiled on platforms without an arch-specificmiod2014-11-201-1/+2
| | | | Makefile.inc (i.e. landisk and m88k)
* Enable the build of GOST routines in libcrypto. Riding upon the Cammeliamiod2014-11-181-6/+6
| | | | libcrypto minor bump.
* Add the Cammelia cipher to libcrypto.miod2014-11-171-2/+2
| | | | | | | | | | | | | | | | | | There used to be a strong reluctance to provide this cipher in LibreSSL in the past, because the licence terms under which Cammelia was released by NTT were free-but-not-in-the-corners, by restricting the right to modify the source code, as well retaining the right to enforce their patents against anyone in the future. However, as stated in http://www.ntt.co.jp/news/news06e/0604/060413a.html , NTT changed its mind and made this code truly free. We only wish there had been more visibility of this, for we could have had enabled Cammelia earlier (-: Licence change noticed by deraadt@. General agreement from the usual LibreSSL suspects. Crank libcrypto.so minor version due to the added symbols.
* GOST crypto algorithms (well, most of them), ported from the removed GOSTmiod2014-11-091-1/+10
| | | | | | | | | | | | engine to regular EVP citizens, contributed by Dmitry Eremin-Solenikov; libcrypto bits only for now. This is a verbatim import of Dmitry's work, and does not compile in this state; the forthcoming commits will address these issues. None of the GOST code is enabled in libcrypto yet, for it still gets compiled with OPENSSL_NO_GOST defined. However, the public header gost.h will be installed.
* Remove SRP code. It contains a bug (this should not surprise anyone), buttedu2014-07-281-5/+1
| | | | | | | | | | | the details are under embargo. The original plan was to wait for the embargo to lift, but we've been waiting for quite some time, and there's no indication of when or even if it will end. No sense in dragging this out any longer. The SRP code has never been enabled in OpenBSD, though I understand it is in use by some other people. However, in light of this and other issues, we're officially saying SRP is outside the scope of libressl. (For now.)
* Remove private_{Camellia,RC4}_set_key FIPS indirection tentacles, as has beenmiod2014-07-121-4/+1
| | | | done for other symmetric algorithms recently.
* move all the feature settings to a common header.tedu2014-07-111-1/+2
| | | | probably ok beck jsing miod
* RSA_NULL used to be a compile option allowing the RSA interfaces to bemiod2014-07-091-2/+2
| | | | | | | | compiled-in, with nonfunctional code, to be able to cope with the RSA patent. However, we don't use this option, and the RSA patent has expired more than 10 years ago, so just drop this piece.
* Remove undocumented _des_crypt() interface and its companion header file,miod2014-07-081-2/+2
| | | | | | | which had never been installed, so it's unlikely something ever used this in the last 15~20 years. ok deraadt@ jsing@ beck@
* Remove BIO_f_reliable(), guilty of playing with EVP_MD_CTX internals itmiod2014-06-241-2/+2
| | | | | should not know anything about. Verified not to be used in ports; riding upon the recent libcrypto major bump.
* Provide support for non-funopen systems.deraadt2014-06-111-2/+2
| | | | ok beck
* Abandon the auto-ENGINE /dev/crypto interface. VIA 3des cbc receivesderaadt2014-06-101-2/+2
| | | | | | | | | | | | | 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
* A few months back there was a big community fuss regarding direct-usederaadt2014-06-021-2/+2
| | | | | | | | | | | | 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
* define LIBRESSL_INTERNAL, and use it to hide the bad stuff from ourselvestedu2014-05-251-1/+2
| | | | ok beck
* When OPENSSL_LOAD_CONF was added it ended up with more #if 0 code,jsing2014-05-161-2/+2
| | | | | | | | | | | more #ifdefs and a new source file that contains a single function. Nuke the #if 0 code that is now a macro and move the single function in evp_acnf.c to c_all.c, which is where the other code lives. While here, tidy evp.h slightly, remove an unnecessary #ifdef __OpenBSD__ and nuke a comment that is now a lie. ok miod@
* Add a ChaCha20-Poly1305 AEAD EVP implementation to libcrypto, from Adamjsing2014-05-151-2/+2
| | | | | | Langley's Chromium OpenSSL patches. ok miod@
* Add an AEAD EVP interface to libcrypto, along with AES-GCM AEADjsing2014-05-151-2/+2
| | | | | | | implementations. This largely pulls in Adam Langley's AEAD patches from Chromium's OpenSSL. ok miod@
* Add poly1305 to libcrypto utilising Andrew Moon's public domainjsing2014-05-141-1/+6
| | | | | | implementation. ok miod@
* Move the `pqueue' part of libcrypto, which is a glorified sorted linked listmiod2014-05-121-6/+1
| | | | | | | | | | | | | of 64-bit data, and only used by DTLS, to libssl where it belongs. Remove pqueue_print() which is a debugging interface and serves no useful purpose, except for the regress test, which grows its own pqueue_print() routine. Bump libcrypto major and libssl minor. WARNING: do not update your tree right now, more changes are coming, which will ride the libcrypto major bump.
* Remove the !SSLASM conditional. Either there is an arch-specific Makefile.inc,miod2014-05-041-4/+2
| | | | | or the !SSLASM list of files applies. This allows for an arch-specific Makefile.inc to not specify SSLASM.
* + e_chacha.c, and bump minormiod2014-05-011-1/+2
|
* Add ChaCha to libcrypto, based on djb's public domain implementation.jsing2014-05-011-1/+6
| | | | ok deraadt@
* We do not need a separate file for two compatibility wrapper functions.jsing2014-04-271-2/+2
| | | | ok miod@
* Make libssl and libcrypto compile with -Werrorbeck2014-04-231-2/+2
| | | | ok miod@
* Do not ask the user to pass either -DB_ENDIAN or -DL_ENDIAN to the compiler,miod2014-04-181-11/+1
| | | | | | | but rather figure out the endianness from <machine/endian.h> automagically; help from guenther@ ok jca@ guenther@ beck@ and the rest of the `Buena SSL rampage club'
* Put back i2d_ASN1_SET() and d2i_ASN1_SET() from the NO_ASN1_OLD prune, as theremiod2014-04-181-1/+2
| | | | | | | are still some 3rd-party code using it, and fixing them is not trivial. As an excuse gift, the memory leaks on failure in resurrected a_set.c have been fixed.
* another round of chemo for the RAND code to provide clarity.tedu2014-04-181-3/+2
| | | | ok deraadt
* egd support is too dangerous to leave where somebody might find it.tedu2014-04-181-2/+2
| | | | ok deraadt.
* Use !defined() rather than empty().miod2014-04-171-2/+2
|
* -Walltedu2014-04-171-1/+3
|
* Ok, there was a need for OPENSSL_cleanse() instead of bzero() to preventmiod2014-04-171-2/+2
| | | | | | | | | | | supposedly smart compilers from optimizing memory cleanups away. Understood. Ok, in case of an hypothetically super smart compiler, OPENSSL_cleanse() had to be convoluted enough for the compiler not to recognize that this was actually bzero() in disguise. Understood. But then why there had been optimized assembler versions of OPENSSL_cleanse() is beyond me. Did someone not trust the C obfuscation?
* Move the machine-specific parts of the libcrypto Makefile to per-arch makefilemiod2014-04-171-104/+6
| | | | | | fragments, to ease maintainance, and see through the fog of bugs. "looks good" deraadt@
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-12-27 13:41:42 +0000