summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Enable the assembler code for BN, which was lost quite some time ago.miod2014-05-042-0/+38
|
* 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-032-0/+92
| | | | | 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-032-0/+90
| | | | | Note that GCM128 Neon code is currently not built (and thus not tested), as the current toolchain does not support Neon instructions.
* Do not compile the neon probe code until __ARM_ARCH__ >= 7. Neon-specific codemiod2014-05-034-4/+28
| | | | will not get referenced if this condition is not met.
* typosmiod2014-05-032-4/+4
|
* Correctly enable Montgomery code.miod2014-05-032-2/+4
|
* now that 5.5 has been released with compatibility for 2b hashes,tedu2014-05-031-2/+2
| | | | switch to generating them by default. prodded by deraadt and sthen
* Update the base64 regress test and enable a test that would previouslyjsing2014-05-031-19/+28
| | | | | | | have resulted in a segfault. Also update the resulting output bytes now that the invalid/corrupt input is detected and rejected; unless you're using BIO_FLAGS_BASE64_NO_NL, in which case you still get a stream of zero value bytes and no way of knowing that the data is invalid/corrupt.
* Add checks for invalid base64 encoded data, specifically relating to thejsing2014-05-032-0/+24
| | | | | | | | | | | | | | | | | | | | | handling of padding. This fixes a crash that can be triggered by feeding base64 data followed by 64 or more padding characters, which results in a negative output length. This issue was reported by David Ramos, although the same bug has been sitting in the OpenSSL RT since 2011: https://rt.openssl.org/Ticket/Display.html?id=2608 Worse still, BIO_read seems to be completely unable to detect that the base64 input was invalid/corrupt - in particular, enabling BIO_FLAGS_BASE64_NO_NL results in a stream of zero value bytes rather than no input (possibly a good replacement for /dev/null...), which could result in nasty consequences. Prior to this fix some zero value bytes were also injected without this flag being enabled. The recently added base64 regress triggers and documents these issues (and also ensures that this change retains functional behaviour).
* 1. Drop support for no minor. This variant doesn't exist anymore.tedu2014-05-031-44/+30
| | | | | | | | | | 2. Pull up the actual minor processing code into the switch that parses it. 3. atoi is actually simpler than strtonum in this case, but check the input beforehand so we don't get unexpected results. 4. Slightly more consistent style between various parse and check and increment operations on salt. ok deraadt
* It is definitly not the correct spelling.jsing2014-05-032-4/+4
|
* KNF.jsing2014-05-038-1864/+1820
|
* Nuke more defines - we have setvbuf() and _IONBF.jsing2014-05-032-16/+0
| | | | ok deraadt@
* KNF.jsing2014-05-038-990/+1028
|
* Initial version of a base64 regress.jsing2014-05-033-1/+382
|
* Enable assembler bits for BN (Montgomery), SHA1 and SHA256.miod2014-05-032-0/+88
| | | | Assembler bits for AES remain commented out as they run slower than the C code.
* Detect Altivec support with the machdep.altivec sysctl rather than setmp andmiod2014-05-034-204/+40
| | | | | a SIGILL handler. Do not attempt to detect and use a 64-bit FPU yet.
* Correctly enable assembler Montgomery routine.miod2014-05-022-2/+4
|
* More use of 64-bit registers which needs to be disabled under OpenBSD.miod2014-05-024-0/+8
|
* Correctly enable assembler Montgomery routine.miod2014-05-022-2/+4
|
* Reenable assembler code for SHA384 and SHA512 now that it no longer miscomputesmiod2014-05-022-6/+6
| | | | things. Worth doing as it's twice faster than the C code.
* The assembly sha512 code detects at runtime if it is running on a 64-bitmiod2014-05-022-0/+12
| | | | | | | | | | | | processor (PA2.0) and, if so, switches to 64-bit code. However, when running under a 32-bit OpenBSD/hppa kernel, there is no guarantee that the upper part of the registers will be preserved accross context switches (or even userland->kernel boundaries), which causes this code to fail. Wrap the generated code within #ifndef __OpenBSD__ in that case, to avoid using the 64-bit code completely. (OpenBSD/hppa64, once stable, will not be affected by this)
* Simple sha{224,256,384,512} test using the FIPS 180-2 test vectors availablemiod2014-05-022-2/+45
| | | | from http://csrc.nist.gov/groups/ST/toolkit/examples.html
* Disable assembler version of SHA512 for now, it produces wrong results.miod2014-05-022-6/+6
|
* Add ChaCha as a cipher.jsing2014-05-021-0/+3
| | | | ok beck@ miod@
* remove crazy #undefs; ok jsingderaadt2014-05-0210-13/+0
|
* Nuke OPENSSL_NO_SOCK since any half sane operating system has sockets.jsing2014-05-029-35/+0
| | | | ok beck@
* Sort and group includes. We also do not need to include openssl/evp.h morejsing2014-05-021-45/+47
| | | | | | than once. ok beck@
* Sort function prototypes and group/sort entries within the functions array.jsing2014-05-021-237/+125
| | | | ok beck@
* Enable use of assembly code for AES, BN (Montgomery), SHA1, SHA256 and SHA512.miod2014-05-012-0/+100
| | | | RC4 assembler code is not used, as it runs about 35% slower than the C code.
* Do not output SOM-specific directives.miod2014-05-0114-0/+80
|
* Remove unreferenced OPENSSL_instrument_bus and OPENSSL_instrument_bus2 routines.miod2014-05-014-210/+0
|
* Make the implicit `l' in `impicit' explicit.miod2014-05-012-2/+2
|
* Enable use of the assembly code for BN (Montgomery) and SHA1.miod2014-05-012-0/+80
|
* Fix include filename to get register name aliases under BSDmiod2014-05-016-36/+6
|
* Pass -Werror in the !BN_LLONG !BN_UMULT_LOHI !BN_UMULT_HIGH case.miod2014-05-012-8/+8
|
* Enable use of the assembly code for AES, BN, SHA1, SHA256 and SHA512.miod2014-05-012-0/+72
|
* dead meatmiod2014-05-014-5056/+0
|
* tweak previous; ok sthenjmc2014-05-011-3/+3
|
* + e_chacha.c, and bump minormiod2014-05-013-3/+4
|
* Update with recently added objects.jsing2014-05-012-0/+36
| | | | ok miod@
* KNF.jsing2014-05-011-324/+296
|
* Nuke unused evptests.txt - the real one is over in regress.jsing2014-05-012-668/+0
| | | | ok miod@
* Provide an EVP implementation for ChaCha.jsing2014-05-0114-0/+233
| | | | ok miod@
* Add ChaCha to libcrypto, based on djb's public domain implementation.jsing2014-05-0110-2/+904
| | | | ok deraadt@
* Add support for the french ANSSI FRP256v1 elliptic curve.miod2014-05-014-2/+70
| | | | | | | | | | While not to be considered a good choice of elliptic curve (refer to http://safecurves.cr.yp.to/ for more details), it is nevertheless deemed a good decision to allow developers with requirements to use such a curve, to be able to do this via a crypto library allowing for much better choices to be made, without having to change (much of) their code to get better crypto. ok beck@ deraadt@
* Add Brainpool elliptic curves. From OpenSSL RT#2239 via ${DAYJOB}.miod2014-05-014-2/+922
| | | | | Be sure to rerun `make includes' after updating. ok tedu@ beck@ deraadt@
* Remove fips_md_init() macro indirection for digest algorithms, used by themiod2014-05-0118-34/+22
| | | | | | | OpenSSL FIPS module to prevent forbidden digests to be allowed. No functional change but readability. ok deraadt@
* nibbles aren't enough random, use bytes. does a better job of pickingtedu2014-05-011-14/+14
| | | | | a free chunk at random and may allow to increase delayed chunk array. ok otto
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-28 22:17:40 +0000