| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
| |
- 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!
|
| |
|
|
|
|
|
|
| |
Reported by David Ramos (and simultaneously to OpenSSL as PR#3339).
ok beck@ logan@
|
|
|
|
|
| |
these files similar in layout to the other md Makefile.inc; no functional
change.
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
ok miod@
|
|
|
|
|
| |
uses the `umul' and `udiv' instructions directly, which are not supported
on v7 processors.
|
|
|
|
| |
ok jmc@
|
|
|
|
| |
fine jmc@
|
| |
|
| |
|
|
|
|
|
| |
or the !SSLASM list of files applies. This allows for an arch-specific
Makefile.inc to not specify SSLASM.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Note that GCM128 Neon code is currently not built (and thus not tested), as
the current toolchain does not support Neon instructions.
|
|
|
|
| |
will not get referenced if this condition is not met.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
| |
|
| |
|
|
|
|
| |
Assembler bits for AES remain commented out as they run slower than the C code.
|
|
|
|
|
| |
a SIGILL handler.
Do not attempt to detect and use a 64-bit FPU yet.
|
| |
|
| |
|
| |
|
|
|
|
| |
things. Worth doing as it's twice faster than the C code.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
| |
RC4 assembler code is not used, as it runs about 35% slower than the C code.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
ok miod@
|
|
|
|
| |
ok miod@
|
|
|
|
| |
ok miod@
|
|
|
|
| |
ok deraadt@
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
| |
Be sure to rerun `make includes' after updating.
ok tedu@ beck@ deraadt@
|
|
|
|
|
|
|
| |
OpenSSL FIPS module to prevent forbidden digests to be allowed.
No functional change but readability.
ok deraadt@
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
|
| |
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@
|