- integrations
- CMake
- ocx_policy
ocx_policy
Weakens the verification posture of every later ocx call in this configure, explicitly.
ocx_policy([ALLOW_UNVERIFIED] [ALLOW_YANKED] [SIGSTORE_TRUSTED_ROOT <file>])New in version 0.4.
The policy is explicit-only. An OCX_NO_VERIFY or OCX_ALLOW_YANKED in the environment is removed from every ocx call. An inherited variable can therefore never weaken a build silently. Nothing is cached, so state the policy in the project listfile on every configure. An empty argument value is an error, because it usually means that a variable is unset.
Call the command before the first ocx_project or ocx_package. A repeated call with identical arguments is a no-op. A call that differs from an earlier one is a fatal error. So is a call that weakens the posture after ocx has already run.
Options
Section titled “Options”ALLOW_UNVERIFIED
Accept packages that fail or lack Sigstore verification. The module sets OCX_NO_VERIFY=1 for the ocx calls.
ALLOW_YANKED
Resolve yanked versions. The module sets OCX_ALLOW_YANKED=1 for the ocx calls.
SIGSTORE_TRUSTED_ROOT <file>
Absolute path of the Sigstore trusted root to verify against. The module sets OCX_SIGSTORE_TRUSTED_ROOT for the ocx calls. A relative path is an error.
Example
Section titled “Example”The test fixture tests/fixtures/runtime_core/case.cmake runs this call.
ocx_policy(ALLOW_YANKED)All commands are listed in the command reference.