summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Enable assembler code for DES. Assembler code for BN is commented out as itmiod2014-05-052-0/+54
| | | | | uses the `umul' and `udiv' instructions directly, which are not supported on v7 processors.
* Improve line wrapping for lines exceeding 80 chars.jim2014-05-0446-192/+284
| | | | ok jmc@
* Remove trailing whitespace.jim2014-05-0455-143/+143
| | | | fine jmc@
* i give up. reuse problem is unfixable. dlg says puppet crashes.tedu2014-05-041-8/+4
|
* 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-032-2/+14
| | | | will not get referenced if this condition is not met.
* typosmiod2014-05-031-2/+2
|
* Correctly enable Montgomery code.miod2014-05-032-2/+4
|
* Add checks for invalid base64 encoded data, specifically relating to thejsing2014-05-031-0/+12
| | | | | | | | | | | | | | | | | | | | | 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).
* It is definitly not the correct spelling.jsing2014-05-031-2/+2
|
* KNF.jsing2014-05-034-932/+910
|
* KNF.jsing2014-05-034-495/+514
|
* 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-032-102/+20
| | | | | 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-022-0/+4
|
* 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-021-0/+6
| | | | | | | | | | | | 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)
* Disable assembler version of SHA512 for now, it produces wrong results.miod2014-05-022-6/+6
|
* 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-017-0/+40
|
* Remove unreferenced OPENSSL_instrument_bus and OPENSSL_instrument_bus2 routines.miod2014-05-012-105/+0
|
* Make the implicit `l' in `impicit' explicit.miod2014-05-011-1/+1
|
* 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-013-18/+3
|
* Pass -Werror in the !BN_LLONG !BN_UMULT_LOHI !BN_UMULT_HIGH case.miod2014-05-011-4/+4
|
* Enable use of the assembly code for AES, BN, SHA1, SHA256 and SHA512.miod2014-05-012-0/+72
|
* dead meatmiod2014-05-012-2528/+0
|
* + e_chacha.c, and bump minormiod2014-05-013-3/+4
|
* Update with recently added objects.jsing2014-05-011-0/+18
| | | | ok miod@
* Nuke unused evptests.txt - the real one is over in regress.jsing2014-05-011-334/+0
| | | | ok miod@
* Provide an EVP implementation for ChaCha.jsing2014-05-016-0/+108
| | | | ok miod@
* Add ChaCha to libcrypto, based on djb's public domain implementation.jsing2014-05-014-1/+320
| | | | ok deraadt@
* Add support for the french ANSSI FRP256v1 elliptic curve.miod2014-05-012-1/+35
| | | | | | | | | | 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-012-1/+461
| | | | | 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-019-17/+11
| | | | | | | OpenSSL FIPS module to prevent forbidden digests to be allowed. No functional change but readability. ok deraadt@
* First pass at removing win64 support from the assembly generating Perljsing2014-04-308-1066/+1
| | | | | | | scripts. We certainly do not need an identical copy of the win64 exception handler in each script (surely one copy would be sufficient). ok miod@
* Remove WIN32, WIN64 and MINGW32 tentacles.miod2014-04-2814-65/+7
| | | | | | | | Also check for _LP64 rather than __arch64__ (the former being more reliable than __LP64__ or __arch64__) to tell 64-bit int platforms apart from 32-bit int platforms. Loosely based upon a diff from Martijn van Duren on tech@
* Leftover includes and local declarations; from Gebruiker Schootmiod2014-04-281-5/+0
|
* typo in commentmiod2014-04-273-3/+3
|
* Use C99 initializers for the various FOO_METHOD structs. More readable, andmiod2014-04-2757-1123/+836
| | | | | | | | | | | | | | | | | | | | | | | | | | | | avoid unreadable/unmaintainable constructs like that: const EVP_PKEY_ASN1_METHOD cmac_asn1_meth = { EVP_PKEY_CMAC, EVP_PKEY_CMAC, 0, "CMAC", "OpenSSL CMAC method", 0,0,0,0, 0,0,0, cmac_size, 0, 0,0,0,0,0,0,0, cmac_key_free, 0, 0,0 }; ok matthew@ deraadt@
* static const char * = "" -> static const char[] = "", to produce shorter code.miod2014-04-273-3/+3
| | | | No functional change.
* Unifdef -U OPENSSL_BUILD_SHLIBCRYPTO, since all it causes under Unix is tomiod2014-04-275-30/+1
| | | | redefine OPENSSL_EXTERN from `extern' to `extern'.
* Put explicit (void) in function declarations and shuffle keywords in somemiod2014-04-2716-18/+18
| | | | | declaration to pass -Wextra, should we want to add it to CFLAGS. No binary change.
* We do not need a separate file for two compatibility wrapper functions.jsing2014-04-273-71/+20
| | | | ok miod@
* Fix leak last commit introduced. Spotted by Sebastian Kapfer.beck2014-04-271-0/+1
|
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-21 12:15:35 +0000