| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
| |
two keys and four IVs to do much magic, is specified as such with test vectors,
but the implementation actually always uses the first key, and the test vectors
were computed with it, so they are wrong.
Fixing the code to match the intended specification would break
interoperability with existing code (assuming such code would exist), so it is
better to remove this interface, which is obviously too complex for mere
mortals if even its author can not implement it correctly.
Riding on the libcrypto major bump.
|
|
|
|
|
|
|
|
| |
ASN1_unpack_string() from the NO_ASN1_OLD purge; turns out that some Ruby
extensions still use them, unfortunately, so we need to give them some more
time to catch up on ``recent'' interfaces.
Riding on the libcrypto major bump.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of 64-bit data, and only used by DTLS, to libssl where it belongs.
Remove pqueue_print() which is a debugging interface and serves no useful
purpose, except for the regress test, which grows its own pqueue_print()
routine.
Bump libcrypto major and libssl minor.
WARNING: do not update your tree right now, more changes are coming, which
will ride the libcrypto major bump.
|
| |
|
| |
|
| |
|
|
|
|
| |
reported by Steven Chamberlain
|
|
|
|
|
| |
Thanks to Google for agreeing to offer the code under more agreeable
licensing terms!
|
|
|
|
| |
Forgotten during yesterday's STRICT_ALIGNMENT cleanup commit.
|
| |
|
| |
|
|
|
|
| |
"fire bomb" tedu@
|
| |
|
|
|
|
|
|
| |
is amusing.
ok deraadt@
|
| |
|
| |
|
| |
|
|
|
|
| |
ok miod@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
than defining it for not (i386 and amd64 (and sometimes s390)) only.
Compile-time tests remain compile-time tests, and runtime-test remain
runtime-test instead of being converted to compile-time tests, per matthew@'s
explicit demand (rationale: this makes sure the compiler checks your code even
if you won't run it).
No functional change except on s390 (which we don't run on) and vax (which we
run on, but noone cares about)
ok matthew@
|
|
|
|
|
| |
reported to openssl by David Ramos (rt 3338)
stealing commit from logan, who's run away. ok miod.
|
|
|
|
| |
i've never worked on codebase so resistant to efforts to improve it.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
makes this compile with OPENSSL_NO_DEPRECATED defined.
ok deraadt@
|
|
|
|
|
| |
beauty sleep. He's probably having a nightmare about this right now....
ok tedu
|
|
|
|
|
|
|
|
|
|
|
| |
- 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.
|