Add osslsigncode package

[Camelron]

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 (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/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

What does the PR accomplish, why was it needed?

osslsigncode is a utility that implements part of the functionality of the Microsoft tool signtool.exe - more exactly the Authenticode signing and timestamping. But osslsigncode is based on OpenSSL and cURL. It can sign and timestamp PE (EXE/SYS/DLL/etc), CAB, CAT and MSI files, as well as signature verification, removal and extraction.

Change Log

• Introduce osslsigncode

Does this affect the toolchain?

NO

Test Methodology

• manually run pipelines:
  • https://dev.azure.com/mariner-org/mariner/_build/results?buildId=505176&view=results
  • https://dev.azure.com/mariner-org/mariner/_build/results?buildId=505171&view=results

[dallasd1]

[nit] would it be possible to link the signing pipeline in the description? @ms-mahuber do you have any thoughts on aligning the PR title to keep release notes consistent?