- Dec 29, 2016
-
-
Matt Caswell authored
The previous commit fixed a bug where the EC point formats extensions did not appear in the ServerHello. This should have been caught by 70-test_sslmessages but that test never tries an EC ciphersuite. This updates the test to do that. Reviewed-by:
Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2153)
-
Matt Caswell authored
This should be sent in the ServerHello if a EC based ciphersuite is negotiated. The relevant flag to do this was missed off in the recent extensions refactor. Fixes GitHub Issue #2133 Reviewed-by:
-
Markus Triska authored
Reviewed-by:
Rich Salz <rsalz@openssl.org> Reviewed-by:
Tim Hudson <tjh@openssl.org> Reviewed-by:
-
- Dec 25, 2016
-
-
Andy Polyakov authored
Reviewed-by:
-
- Dec 22, 2016
-
-
Todd Short authored
Reviewed-by:
-
- Dec 21, 2016
-
-
Richard Levitte authored
We should move it back to the BORINGTEST build when we are approaching interoperability. Reviewed-by:
Kurt Roeckx <kurt@openssl.org> Reviewed-by:
-
- Dec 20, 2016
-
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
For now, checking that the size is non-zero will suffice. Reviewed-by:
-
- Dec 19, 2016
-
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Andy Polyakov authored
Reviewed-by:
-
- Dec 18, 2016
-
-
Kurt Roeckx authored
Reviewed-by: -
Kurt Roeckx authored
Found by oss-fuzz Reviewed-by: -
Finn Hakansson authored
Reviewed-by:
-
- Dec 16, 2016
-
-
Richard Levitte authored
In some cases, both client and server end of the test can end up in SSL_ERROR_WANT_READ and never get out of it, making the test spin. Detect it and give up instead of waiting endlessly. Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
When built with --strict-warnings and the Linux kernel headers don't match the kernel version, the preprocessor warnings in engines/afalg/e_afalg.c cause compilation errors. Use the macro PEDANTIC to avoid those warnings in that case. Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Richard Levitte authored
Reviewed-by:
-
Kurt Roeckx authored
Also send a SNI extension in the client so the fuzzer can react to it. Reviewed-by: -
Kurt Roeckx authored
We use those parameters for calculating the coverage. Reviewed-by: -
Kurt Roeckx authored
This make sure that the coverage is the same for the fuzzers and this coverage target Reviewed-by:
-
- Dec 15, 2016
-
-
Kurt Roeckx authored
Calling it with lenght 0 and NULL as source is undefined behaviour. Reviewed-by: -
Andy Polyakov authored
chacha/asm/chacha-x86_64.pl: refine nasm version detection logic. Reviewed-by: -
Andy Polyakov authored
Reviewed-by: -
Andy Polyakov authored
Reviewed-by:
-
- Dec 14, 2016
-
-
Rich Salz authored
More importantly, port CRL test from boringSSL crypto/x509/x509_test.cc Reviewed-by:
-
Dr. Stephen Henson authored
Add options to check the function and reason code matches expected values. Reviewed-by:
-
- Dec 13, 2016
-
-
Rich Salz authored
Reviewed-by:
-
Rich Salz authored
find-doc-nits warns if you don't give a "what to do flag" Don't use regexps for section names, just strings: More consistency. Rename "COMMAND OPTIONS" to OPTIONS. Fix a couple of other nit-level things. Reviewed-by:
-
- Dec 12, 2016
-
-
Azat Khuzhin authored
Fixes: 8d00e30f ("Don't try to init dasync internally") Reviewed-by:
Matt Caswell <matt@openssl.org> CLA: trivial
-
Dmitry Belyavskiy authored
Reviewed-by:
-
Paul Hovey authored
Reviewed-by:
-
Paul Hovey authored
fix undoes errors introduced by https://github.com/openssl/openssl/commit/fc6076ca272f74eb1364c29e6974ad5da5ef9777?diff=split#diff-1014acebaa2c13d44ca196b9a433ef2eR184 Reviewed-by:
-
Benjamin Kaduk authored
Commit 0cd0a820 removed this macro along with many unused function and reason codes; ERR_FATAL_ERROR() was not used in the tree, but did have external consumers. Add it back to restore the API compatibility and avoid breaking applications for no internal benefit. Reviewed-by:
-
Matt Caswell authored
SSL_clear() was resetting numwpipes to 0, but not freeing any allocated memory for existing write buffers. Fixes #2026 Reviewed-by: -
Andy Polyakov authored
$1<<32>>32 worked fine with either 32- or 64-bit perl for a good while, relying on quirk that [pure] 32-bit perl performed it as $1<<0>>0. But this apparently changed in some version past minimally required 5.10, and operation result became 0. Yet, it went unnoticed for another while, because most perl package providers configure their packages with -Duse64bitint option. Reviewed-by: -
Andy Polyakov authored
Reviewed-by: -
Andy Polyakov authored
Reviewed-by:
-
- Dec 10, 2016
-
-
Davide Galassi authored
CLA: trivial Reviewed-by:
-
