| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
- add macro CHECK_GOTO
- unify function return code to rc
- add err: label for error goto
ok bcook@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This regress bntest.c patch is originally from master branch of OpenSSL.
- dca2e0e test/bntest.c: regression test for CVE-2016-7055.
- 3e7a496 test/bntest.c: regression test for carry bug in bn_sqr8x_internal.
These tests were added for these commit.
- 2fac86d bn/asm/x86_64-mont.pl: fix for CVE-2016-7055 (Low severity).
- 3f4bcf5 bn/asm/x86_64-mont5.pl: fix carry bug in bn_sqr8x_internal.
ok beck@
|
|
|
|
| |
hook it up yet
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
matter for constant time, and make the public interface only used
external to the library.
This moves us to a model where the important things are constant time
versions unless you ask for them not to be, rather than the opposite.
I'll continue with this method by method.
Add regress tests for same.
ok jsing@
|
|
|
|
| |
therefore appears to break in bluhm's test setup
|
| |
|
| |
|
|
|
|
|
|
| |
it is linked against change.
ok beck@ jsing@
|
|
|
|
|
| |
code now lives. Also unbreak the regress following the symbol hiding
changes in libssl.
|
|
|
|
|
|
|
| |
New tests that various BIGNUM methods behave correctly on zero/even inputs.
from OpenSSL
ok beck@
|
| |
|
|
|
|
| |
from Kinichiro Inoguchi
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BN_mod_word() can return incorrect results if the supplied modulus is
too big, so we need to fall back to BN_div_word.
Now that BN_mod_word may fail, handle errors properly update the man page.
Thanks to Brian Smith for pointing out these fixes from BoringSSL:
https://boringssl.googlesource.com/boringssl/+/67cb49d045f04973ddba0f92fe8a8ad483c7da89
https://boringssl.googlesource.com/boringssl/+/44bedc348d9491e63c7ed1438db100a4b8a830be
ok beck@
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This removes support for DSA_FLAG_NO_EXP_CONSTTIME, DH_FLAG_NO_EXP_CONSTTIME,
and RSA_FLAG_NO_CONSTTIME flags, making all of these operations unconditionally
constant-time.
Based on the original patch by César Pereid. ok beck@
|
|
|
|
| |
ok beck@ jsing@
|
| |
|
|
|
|
| |
plaintext for the regress test case.
|
| |
|
|
|
|
| |
ok beck@
|
|
|
|
|
|
|
|
|
| |
"ChaCha20 and Poly1305 for IETF Protocols", introduced a modified AEAD
construction that is incompatible with the common style that has been
already used in TLS with EVP_aead_chacha20_poly1305(). The IETF
version also adds a constant (salt) that is prepended to the nonce.
OK mikeb@ jsing@
|
| |
|
| |
|
|
|
|
|
| |
relying upon previously included headers to do this, to enhance portability;
from Pascal Cuoq, libressl github pull request #52
|
| |
|
|
|
|
|
|
|
| |
pointer - because, you know, you might want to set a string on a NULL
object. The previous implementation apparently allowed this as a way of
testing if the string was valid... probably because the *_check() functions
are only useable after the string has already been set.
|
|
|
|
| |
ASN1_UTCTIME_set_string() twice instead.
|
| |
|
| |
|
|
|
|
|
|
|
| |
per RFC 5380 in an X509. RFC 5280 states that all times before 2050 must
be specified as a UTCtime, not a Generalized time, and all times after must
be a UTC time. By extension this also means the smallest time allowed
per RFC 5280 is 500101000000Z and the largest is 99991231235959Z..
|
|
|
|
|
|
| |
Note some of these will yet fail with the current libcrypto as the current
X509_cmp_time is not RFC5280 compliant
ok jsing@
|
|
|
|
|
|
|
|
|
| |
By default, "openssl sha" used SHA-0. However, it was possible to use
the form "openssl sha -sha256" to run SHA-256 instead. The regression
test used this form. Since we removed SHA-0 support, the regress tests
should now call "openssl <digest>".
ok guenther@, bcook@
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
MD4 should have been removed a long time ago. Also, RFC 6150 moved it to
historic in 2011. Rides the major crank from removing SHA-0.
Discussed with many including beck@, millert@, djm@, sthen@
ok jsing@, input + ok bcook@
|
| |
|
|
|
|
|
|
|
| |
SHA-0 was withdrawn shortly after publication 20 years ago and replaced
with SHA-1. This will require a major crank.
ok bcook@, jsing@
|
| |
|
| |
|
|
|
|
| |
ok jsing@
|
| |
|
| |
|
|
|
|
|
| |
It was the only thing preventing -Werror from building on some systems due to
the unchecked asprintf's.
|
| |
|