Skip to content

install.sh should make strict verification and signer fingerprint policy explicit #3502

Description

@Widthdom

Problem

Release checksum signature and GitHub attestation verification are optional by default. When tooling or fingerprint configuration is absent, the installer warns and continues.

Evidence

  • verify_release_attestation warns and continues if gh is unavailable unless CDIDX_REQUIRE_ATTESTATION=1.
  • verify_checksum_signature warns and continues if gpg is unavailable or if no expected fingerprint is configured unless strict mode is enabled.

Expected behavior

Document and enforce a clear default verification policy, including whether public release installs should fail closed, how the expected GPG fingerprint is distributed, and how strict/compatibility modes are selected.

Labels

enhancement, security

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions