The trusted_task policy rules emit the message "Code tampering detected" in two scenarios:
- When a trusted artifact input was not produced by the pipeline (
valid_trusted_artifact_inputs rule in policy/release/trusted_task/trusted_task.rego around line 208)
- When an untrusted PipelineTask is found in the build chain (around line 552)
This wording is overly alarming and can cause unnecessary panic for users whose pipelines simply have a configuration issue or include a task not yet on the trusted list.
The message should be replaced with something more accurate and measured, such as "Untrusted task or input detected in build pipeline" or similar.
The corresponding test expectations in trusted_task_test.rego and documentation in release_trusted_task.adoc must also be updated.
The
trusted_taskpolicy rules emit the message "Code tampering detected" in two scenarios:valid_trusted_artifact_inputsrule inpolicy/release/trusted_task/trusted_task.regoaround line 208)This wording is overly alarming and can cause unnecessary panic for users whose pipelines simply have a configuration issue or include a task not yet on the trusted list.
The message should be replaced with something more accurate and measured, such as "Untrusted task or input detected in build pipeline" or similar.
The corresponding test expectations in
trusted_task_test.regoand documentation inrelease_trusted_task.adocmust also be updated.