openssl/test, branch OpenSSL_1_1_0g

afalg: Fix kernel version check

2017-10-31T10:22:06Z

The check should reject kernel versions < 4.1.0, not <= 4.1.0. The issue was spotted on OpenSUSE 42.1 Leap, since its linux/version.h header advertises 4.1.0. CLA: trivial Fixes: 7f458a48 ("ALG: Add AFALG engine") Signed-off-by: Baptiste Jonglez Reviewed-by: Matt Caswell Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/4618)

Backport key redirection test from master branch

2017-10-13T22:07:49Z

Reviewed-by: Rich Salz Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/4520)

Skip ssl-tests/19-mac-then-encrypt.conf for no-tls1_2

2017-10-13T00:22:16Z

The second set of tests in that configuration uses the AES-SHA256 ciphers, which are only available for TLS 1.2. Thus, when TLS 1.2 is disabled, there are no ciphers available and the handshake fails with an internal error. Apply the same treatment as for 13-fragmentation.conf, which uses the same ciphers. Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/4526)

Fix util/perl/OpenSSL/Test.pm input variable overwrite

2017-10-09T19:22:16Z

Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/4507) (cherry picked from commit 9b9a8a712d64e35a337b22869288f246b5580c73)

Test mac-then-encrypt

2017-10-05T07:29:28Z

Verify that the encrypt-then-mac negotiation is handled correctly. Additionally, when compiled with no-asm, this test ensures coverage for the constant-time MAC copying code in ssl3_cbc_copy_mac. The proxy-based CBC padding test covers that as well but it's nevertheless better to have an explicit handshake test for mac-then-encrypt. Reviewed-by: Andy Polyakov (cherry picked from commit b3618f44a7b8504bfb0a64e8a33e6b8e56d4d516)

recipes/25-test_verify.t: reformat.

2017-09-30T20:17:51Z

Reviewed-by: Richard Levitte (Merged from https://github.com/openssl/openssl/pull/4411)

Guard against DoS in name constraints handling.

2017-09-30T20:17:36Z

This guards against the name constraints check consuming large amounts of CPU time when certificates in the presented chain contain an excessive number of names (specifically subject email names or subject alternative DNS names) and/or name constraints. Name constraints checking compares the names presented in a certificate against the name constraints included in a certificate higher up in the chain using two nested for loops. Move the name constraints check so that it happens after signature verification so peers cannot exploit this using a chain with invalid signatures. Also impose a hard limit on the number of name constraints check loop iterations to further mitigate the issue. Thanks to NCC for finding this issue. Fix written by Martin Kreichgauer. Reviewed-by: Rich Salz Reviewed-by: Andy Polyakov (Merged from https://github.com/openssl/openssl/pull/4411) (cherry picked from commit 8545051c3652bce7bb962afcb6879c4a6288bc67) Resolved conflicts: crypto/x509v3/v3_ncons.c test/recipes/25-test_verify.t

Allow DH_set0_key with only private key.

2017-09-27T15:28:24Z

The pub_key field for DH isn't actually used in DH_compute_key at all. (Note the peer public key is passed in as as BIGNUM.) It's mostly there so the caller may extract it from DH_generate_key. It doesn't particularly need to be present if filling in a DH from external parameters. The check in DH_set0_key conflicts with adding OpenSSL 1.1.0 to Node. Their public API is a thin wrapper over the old OpenSSL one: https://nodejs.org/api/crypto.html#crypto_class_diffiehellman They have separate setPrivateKey and setPublicKey methods, so the public key may be set last or not at all. In 1.0.2, either worked fine since operations on DH objects generally didn't use the public key. (Like with OpenSSL, Node's setPublicKey method is also largely a no-op, but so it goes.) In 1.1.0, DH_set0_key prevents create a private-key-only DH object. (cherry picked from commit d58ad9a2a287d1c0bc99ba63c997eed88cc161b5) Reviewed-by: Rich Salz Reviewed-by: Bernd Edlinger (Merged from https://github.com/openssl/openssl/pull/4425)

Fix OpenSSL::Test::Utils::config to actualy load the config data

2017-09-01T20:53:16Z

Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/4319) (cherry picked from commit 607f4d564f9540cda6cf5b127f2414625a11741a)

evp_test.c: Add PrivPubKeyPair negative tests

2017-08-21T10:19:17Z

Reviewed-by: Rich Salz Reviewed-by: Matt Caswell (Merged from https://github.com/openssl/openssl/pull/3246)