summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* don't free memory unless we allocated it.tedu2014-05-071-2/+4
| | | | | reported to openssl by David Ramos (rt 3338) stealing commit from logan, who's run away. ok miod.
* with the first bug it uncovered fixed, clear all bignums again.tedu2014-05-071-17/+9
| | | | i've never worked on codebase so resistant to efforts to improve it.
* in BN_clear_free, don't cleanse the data if the static data flag is set.tedu2014-05-071-3/+2
| | | | | | | | much debugging work done by otto. ok miod otto. side note: BN_FLG_STATIC_DATA doesn't actually mean the data is static. it's also used to indicate the data may be secretly shared behind your back as a sort of poor man's refcounting, but without the refcounting.
* KNF.jsing2014-05-0714-944/+984
|
* revert, thanks sthentedu2014-05-071-9/+17
|
* add additional includes from eng_cryptodev.cjsg2014-05-071-0/+5
| | | | | makes this compile with OPENSSL_NO_DEPRECATED defined. ok deraadt@
* miod forgot about fcrypt_b.c being needed, before he went off to get hisderaadt2014-05-072-2/+4
| | | | | beauty sleep. He's probably having a nightmare about this right now.... ok tedu
* Assorted cleanups:miod2014-05-061-14/+4
| | | | | | | | | | | - replace hardcoded sizes with sizeof() - pqueue_find() apparently used to need to keep track of the previous node when iterating, which causes its logic to be complicated. However, nowadays it only needs to iterate, so replace with a straightforward, much readable logic. - remove #if 0'ed code From ``sin'' from 2f30 dot org on tech@, thanks!
* Remove broken-by-design testmiod2014-05-061-95/+0
|
* Make sure PKCS7_get_octet_string() return values are checked for NULL.miod2014-05-061-2/+10
| | | | | | Reported by David Ramos (and simultaneously to OpenSSL as PR#3339). ok beck@ logan@
* Sort CFLAGS, SRC and SSLASM stanzas by the directories they apply to, to makemiod2014-05-064-136/+166
| | | | | these files similar in layout to the other md Makefile.inc; no functional change.
* knf approximationtedu2014-05-0624-8619/+9136
|
* inspired by a cloudflare diff, cleanse old memory when expanding a bignum.tedu2014-05-051-17/+9
| | | | | | however, instead of trying to audit all the places where a secret bignum is used, apply the big hammer and clear all bignums when freed. ok deraadt miod
* Sort and group includes.jsing2014-05-052-10/+11
|
* Repair BIO_socket_nbio operation.jsing2014-05-051-2/+3
| | | | ok miod@
* 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@
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-25 16:40:24 +0000