openssl speed fixes

[tobiasb-ms]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

With the symcrypt provider installed, openssl speed has a couple problems.

First, there are intermittent (but frequent) segfaults in openssl speed ecdh and openssl speed ffdh. This is fixed by upstream pull openssl/openssl#26976. We fix that by taking that patch.

Second, there are several warnings, the root cause of which also makes certain speed test be skipped. This boils down to a feature gap between symcrypt and default provider. For now, we will patch out the specific tests that are warning/bailing, but as those features come online in symcrypt we'll modify/remove that patch.

Change Log

• Add upstream patch openssl/openssl@782912c to fix seg faults.
• Add patch that disables specific speed tests that symcrypt does not yet support.
• Bump release and package manifests.

Does this affect the toolchain?

YES

Associated issues

• ADO: https://microsoft.visualstudio.com/OS/_queries/edit/56729282

Test Methodology

• Built locally
• Giant Build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=765144&view=results
  From that giant build, I grabbed four marketplace VMs and created custom marketplace images with them:

1. amd64-non-fips
2. amd64-fips
3. arm64-non-fips
4. arm64-fips

For each, I validated:

1. It was in the correct fips mode
2. Fips mode could be enabled/disabled
3. symcrypt provider is present by default and for non-fips images can be removed.
4. basic encrypt/decrypt and sign/validate worked
5. openssl speed runs correctly
6. go tests with the system provider run properly

• New Giant Build After Rebasing: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=765144&view=results