Age | Commit message (Collapse) | Author | |
---|---|---|---|
2014-05-05 | Enable assembler code for DES. Assembler code for BN is commented out as it | Miod Vallat | |
uses the `umul' and `udiv' instructions directly, which are not supported on v7 processors. | |||
2014-05-04 | Improve line wrapping for lines exceeding 80 chars. | Jim Razmus II | |
ok jmc@ | |||
2014-05-04 | Remove trailing whitespace. | Jim Razmus II | |
fine jmc@ | |||
2014-05-04 | i give up. reuse problem is unfixable. dlg says puppet crashes. | Ted Unangst | |
2014-05-04 | Enable the assembler code for BN, which was lost quite some time ago. | Miod Vallat | |
2014-05-03 | Enable assembler code for AES, DES, GCM, SHA1, SHA256 and SHA512. | Miod Vallat | |
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. | |||
2014-05-03 | Enable assembler code for AES, BN (Montgomery), GCM128, SHA1, SHA256 and SHA512. | Miod Vallat | |
Note that GCM128 Neon code is currently not built (and thus not tested), as the current toolchain does not support Neon instructions. | |||
2014-05-03 | Do not compile the neon probe code until __ARM_ARCH__ >= 7. Neon-specific code | Miod Vallat | |
will not get referenced if this condition is not met. | |||
2014-05-03 | typos | Miod Vallat | |
2014-05-03 | Correctly enable Montgomery code. | Miod Vallat | |
2014-05-03 | Add checks for invalid base64 encoded data, specifically relating to the | Joel Sing | |
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). | |||
2014-05-03 | It is definitly not the correct spelling. | Joel Sing | |
2014-05-03 | KNF. | Joel Sing | |
2014-05-03 | KNF. | Joel Sing | |
2014-05-03 | Enable assembler bits for BN (Montgomery), SHA1 and SHA256. | Miod Vallat | |
Assembler bits for AES remain commented out as they run slower than the C code. | |||
2014-05-03 | Detect Altivec support with the machdep.altivec sysctl rather than setmp and | Miod Vallat | |
a SIGILL handler. Do not attempt to detect and use a 64-bit FPU yet. | |||
2014-05-02 | Correctly enable assembler Montgomery routine. | Miod Vallat | |
2014-05-02 | More use of 64-bit registers which needs to be disabled under OpenBSD. | Miod Vallat | |
2014-05-02 | Correctly enable assembler Montgomery routine. | Miod Vallat | |
2014-05-02 | Reenable assembler code for SHA384 and SHA512 now that it no longer miscomputes | Miod Vallat | |
things. Worth doing as it's twice faster than the C code. | |||
2014-05-02 | The assembly sha512 code detects at runtime if it is running on a 64-bit | Miod Vallat | |
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) | |||
2014-05-02 | Disable assembler version of SHA512 for now, it produces wrong results. | Miod Vallat | |
2014-05-01 | Enable use of assembly code for AES, BN (Montgomery), SHA1, SHA256 and SHA512. | Miod Vallat | |
RC4 assembler code is not used, as it runs about 35% slower than the C code. | |||
2014-05-01 | Do not output SOM-specific directives. | Miod Vallat | |
2014-05-01 | Remove unreferenced OPENSSL_instrument_bus and OPENSSL_instrument_bus2 routines. | Miod Vallat | |
2014-05-01 | Make the implicit `l' in `impicit' explicit. | Miod Vallat | |
2014-05-01 | Enable use of the assembly code for BN (Montgomery) and SHA1. | Miod Vallat | |
2014-05-01 | Fix include filename to get register name aliases under BSD | Miod Vallat | |
2014-05-01 | Pass -Werror in the !BN_LLONG !BN_UMULT_LOHI !BN_UMULT_HIGH case. | Miod Vallat | |
2014-05-01 | Enable use of the assembly code for AES, BN, SHA1, SHA256 and SHA512. | Miod Vallat | |
2014-05-01 | dead meat | Miod Vallat | |
2014-05-01 | + e_chacha.c, and bump minor | Miod Vallat | |
2014-05-01 | Update with recently added objects. | Joel Sing | |
ok miod@ | |||
2014-05-01 | Nuke unused evptests.txt - the real one is over in regress. | Joel Sing | |
ok miod@ | |||
2014-05-01 | Provide an EVP implementation for ChaCha. | Joel Sing | |
ok miod@ | |||
2014-05-01 | Add ChaCha to libcrypto, based on djb's public domain implementation. | Joel Sing | |
ok deraadt@ | |||
2014-05-01 | Add support for the french ANSSI FRP256v1 elliptic curve. | Miod Vallat | |
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@ | |||
2014-05-01 | Add Brainpool elliptic curves. From OpenSSL RT#2239 via ${DAYJOB}. | Miod Vallat | |
Be sure to rerun `make includes' after updating. ok tedu@ beck@ deraadt@ | |||
2014-05-01 | Remove fips_md_init() macro indirection for digest algorithms, used by the | Miod Vallat | |
OpenSSL FIPS module to prevent forbidden digests to be allowed. No functional change but readability. ok deraadt@ | |||
2014-04-30 | First pass at removing win64 support from the assembly generating Perl | Joel Sing | |
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@ | |||
2014-04-28 | Remove WIN32, WIN64 and MINGW32 tentacles. | Miod Vallat | |
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@ | |||
2014-04-28 | Leftover includes and local declarations; from Gebruiker Schoot | Miod Vallat | |
2014-04-27 | typo in comment | Miod Vallat | |
2014-04-27 | Use C99 initializers for the various FOO_METHOD structs. More readable, and | Miod Vallat | |
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@ | |||
2014-04-27 | static const char * = "" -> static const char[] = "", to produce shorter code. | Miod Vallat | |
No functional change. | |||
2014-04-27 | Unifdef -U OPENSSL_BUILD_SHLIBCRYPTO, since all it causes under Unix is to | Miod Vallat | |
redefine OPENSSL_EXTERN from `extern' to `extern'. | |||
2014-04-27 | Put explicit (void) in function declarations and shuffle keywords in some | Miod Vallat | |
declaration to pass -Wextra, should we want to add it to CFLAGS. No binary change. | |||
2014-04-27 | We do not need a separate file for two compatibility wrapper functions. | Joel Sing | |
ok miod@ | |||
2014-04-27 | Fix leak last commit introduced. Spotted by Sebastian Kapfer. | Bob Beck | |
2014-04-26 | Replace all use of ERR_add_error_data with ERR_asprintf_error_data. | Bob Beck | |
This avoids a lot of ugly gymnastics to do snprintfs before sending the bag of strings to ERR, and eliminates at least one place in dso_dlfctn.c where it was being called with the incorrect number of arguments and using random things off the stack as addresses of strings. ok krw@, jsing@ |