openssl, branch openssl-3.0.3

Prepare for release of 3.0.3

2022-05-03T13:32:01Z

Reviewed-by: Tomas Mraz Release: yes

make update

2022-05-03T13:32:01Z

Reviewed-by: Tomas Mraz Release: yes

CHANGES.md: Attribute the OPENSSL_LH_flush() fix properly

2022-05-03T13:03:57Z

Reviewed-by: Matt Caswell Release: yes

Update copyright year

2022-05-03T12:36:42Z

Reviewed-by: Tomas Mraz Release: yes

Update CHANGES and NEWS for new release

2022-05-03T12:28:07Z

Reviewed-by: Tomas Mraz Release: yes

Update Paul's pgp key signature

2022-05-03T11:37:10Z

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

c_rehash: Do not use shell to invoke openssl

2022-05-03T10:08:36Z

Except on VMS where it is safe. This fixes CVE-2022-1292. Reviewed-by: Matthias St. Pierre Reviewed-by: Matt Caswell

Fix the RC4-MD5 cipher

2022-05-03T09:54:29Z

A copy&paste error meant that the RC4-MD5 cipher (used in TLS) used the TLS AAD data as the MAC key. CVE-2022-1434 Fixes #18112 Reviewed-by: Tomas Mraz Reviewed-by: Shane Lontis Reviewed-by: Matt Caswell

Test ocsp with invalid responses and the "-no_cert_checks" option

2022-05-03T09:54:13Z

The "-no_cert_checks" option causes the flag OCSP_NOCHECKS to be set. The bug fixed in the previous commit will cause the ocsp app to respond with a success result in the case when the OCSP response signing certificate fails to verify and -no_cert_checks is used - so we test that it fails in this case. Reviewed-by: Paul Dale Reviewed-by: Tomas Mraz Reviewed-by: Matt Caswell

Fix OCSP_basic_verify signer certificate validation

2022-05-03T09:54:03Z

The function `OCSP_basic_verify` validates the signer certificate on an OCSP response. The internal function, ocsp_verify_signer, is responsible for this and is expected to return a 0 value in the event of a failure to verify. Unfortunately, due to a bug, it actually returns with a postive success response in this case. In the normal course of events OCSP_basic_verify will then continue and will fail anyway in the ocsp_check_issuer function because the supplied "chain" value will be empty in the case that ocsp_verify_signer failed to verify the chain. This will cause OCSP_basic_verify to return with a negative result (fatal error). Normally in the event of a failure to verify it should return with 0. However, in the case of the OCSP_NOCHECKS flag being used, OCSP_basic_verify will return with a positvie result. This could lead to callers trusting an OCSP Basic response when it should not be. CVE-2022-1343 Fixes #18053 Reviewed-by: Paul Dale Reviewed-by: Tomas Mraz Reviewed-by: Matt Caswell