summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/crypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix ia64 cross-gcc target.tobiasu2014-05-271-0/+3
| | | | | | opensslconf.h is just a dummy, we're lightyears away from working userspace. ok deraadt@
* "for every change..."tedu2014-05-251-1/+1
|
* 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-122-8/+3
| | | | | | | | | | | | | 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.
* miod forgot about fcrypt_b.c being needed, before he went off to get hisderaadt2014-05-071-1/+2
| | | | | beauty sleep. He's probably having a nightmare about this right now.... ok tedu
* Sort CFLAGS, SRC and SSLASM stanzas by the directories they apply to, to makemiod2014-05-062-68/+83
| | | | | these files similar in layout to the other md Makefile.inc; no functional change.
* Enable assembler code for DES. Assembler code for BN is commented out as itmiod2014-05-051-0/+27
| | | | | uses the `umul' and `udiv' instructions directly, which are not supported on v7 processors.
* Enable the assembler code for BN, which was lost quite some time ago.miod2014-05-041-0/+19
|
* 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.
* Enable assembler code for AES, DES, GCM, SHA1, SHA256 and SHA512.miod2014-05-031-0/+46
| | | | | The sparcv9 BN code is not enabled, as it expects to run on a 32-bit userland and will need to be fixed for 64-bit userland first.
* Enable assembler code for AES, BN (Montgomery), GCM128, SHA1, SHA256 and SHA512.miod2014-05-031-0/+45
| | | | | Note that GCM128 Neon code is currently not built (and thus not tested), as the current toolchain does not support Neon instructions.
* Correctly enable Montgomery code.miod2014-05-031-1/+2
|
* Enable assembler bits for BN (Montgomery), SHA1 and SHA256.miod2014-05-031-0/+44
| | | | Assembler bits for AES remain commented out as they run slower than the C code.
* Correctly enable assembler Montgomery routine.miod2014-05-021-1/+2
|
* Correctly enable assembler Montgomery routine.miod2014-05-021-1/+2
|
* Reenable assembler code for SHA384 and SHA512 now that it no longer miscomputesmiod2014-05-021-3/+3
| | | | things. Worth doing as it's twice faster than the C code.
* Disable assembler version of SHA512 for now, it produces wrong results.miod2014-05-021-3/+3
|
* Enable use of assembly code for AES, BN (Montgomery), SHA1, SHA256 and SHA512.miod2014-05-011-0/+50
| | | | RC4 assembler code is not used, as it runs about 35% slower than the C code.
* Enable use of the assembly code for BN (Montgomery) and SHA1.miod2014-05-011-0/+40
|
* Enable use of the assembly code for AES, BN, SHA1, SHA256 and SHA512.miod2014-05-011-0/+36
|
* + e_chacha.c, and bump minormiod2014-05-012-2/+3
|
* 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@
* Chop off more SSLv2 tentacles and start fixing and noting y2038 issues.guenther2014-04-201-1/+1
| | | | | | | APIs that pass times as longs will have to change at some point... Bump major on both libcrypto and libssl. ok tedu@
* 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'
* first round of static config. ok miodtedu2014-04-1813-559/+0
|
* 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.
* we need to cranktedu2014-04-181-1/+1
|
* 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-173-104/+124
| | | | | | fragments, to ease maintainance, and see through the fog of bugs. "looks good" deraadt@
* Fully kill FIPS API. Forcible certification conflicts with the goals of atedu2014-04-171-2/+2
| | | | | | free software project. ok beck deraadt Ports calling FIPS_mode_set(1): mongodb
* No need to define ANSI_SOURCE and NO_ERR. TERMIOS kept until ui/ui_openssl.cmiod2014-04-161-2/+2
| | | | gets a second trim.
* No need to build with -DOPENSSL_NO_CAPIENG and -DOPENSSL_NO_HW_xxx for allmiod2014-04-161-10/+1
| | | | now removed engines.
* Remove DES_read_password and DES_read_2passwords which are `modern' flavoursmiod2014-04-161-2/+1
| | | | | | of des_old.h routines, acting as wrappers about the OpenSSL UI API. Nothing should use these functions directly. Riding the recent libcrypto major bump (in a `des' car).
* Your operating system memory allocation functions are your friend. If theybeck2014-04-161-2/+2
| | | | | | | | are not please fix your operating system. Replace mem.c with an API-compatible wrapper that just calls the system functions and does not allow a one word modification of a variable in a running shared library to turn on memory debug functions that expose things that should not be seen. ok tedu@
* don't even pretend to build md2, seed, or jpaketedu2014-04-151-17/+3
| | | | ok beck deraadt
* The more you remove Chtulhu^WVMS tentacles, the more there aremiod2014-04-1513-26/+0
|
* 12 years ago, old_des.h was used to provide compatibility with libdes.tedu2014-04-151-3/+2
| | | | | | | | | | | | The man page says "Compatibility des_ functions are provided for a short while" and indeed even the original commit message says "The compatibility functions will be removed in some future release, at the latest in version 1.0." So here we are, a short while later. Now I've only been an OpenBSD developer for 11 years, one year less than this header has existed, but in that brief time, I've learned a thing or two about deleting obsolete code. It doesn't delete itself. And worse, people will continue using it until you force them onto a better path.
* Crank major for libcrypto and libssl; more symbol removals to occur during themiod2014-04-151-2/+2
| | | | | next few moments, don't rush your update. Requested by deraadt@
* The NO_ASN1_OLD define was introduced in 0.9.7, 8 years ago, to allow formiod2014-04-151-2/+2
| | | | | | | | | | obsolete (and mostly internal) routines to be compiled out. We don't expect any reasonable software to stick to these interfaces, so better clean up the view and unifdef -DNO_ASN1_OLD. The astute reader will notice the existence of NO_OLD_ASN1 which serves a similar purpose, but is more entangled. Its time will come, soon.
* Just like every web browser expands until it can read mail, every modularmiod2014-04-151-3/+3
| | | | | | | | | | | | | | | library expands until it has its own dlfcn wrapper, and libcrypto is no exception. Remove the non-dlfcn DSO methods. This causes public DSO_METHOD_{beos,dl,vms,win32} to disappear (major bump coming soon). Note that portable software ought to use DSO_METHOD_openssl instead of picking the backend directly (which makes one wonder why the backends are exposed, as it is unlikely that more than one can work on your system). ok beck@ deraadt@
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-27 15:27:34 +0000