ENH,BLD,SEC: sigstore, SLSA

[westurner]

Users can verify lineageOS-built software artifacts with sigstore (and someday, SLSA) manually and with the lineageos updater android app (because sha256 without crytographic signatures is not good enough according to TUF, Sigstore, and SLSA)

• https://wiki.lineageos.org/signing_builds
• [ ] Decide whether to start with SLSA, Sigstore, or just TUF
  • SLSA supports Sigstore
  • Sigstore depends on TUF to be verified itself
  • blockcerts/cert-verifier-js is another approach (built with W3C Verfiable Credentials and W3C DID Decentralized Identifier keys instead of OIDC OpenID Connect)
• [ ] Sign LineageOS build list json files
  • https://download.lineageos.org/api/v2/devices/sunfish/builds
• [ ] Sign LineageOS CI ROM builds
  • [ ] Upload artifact signatures to a log
• [ ] Update lineageos-infra/updater?
• [ ] Verify LineageOS ROM downloads with a (python?) CLI tool by default, and optionally
  • [ ] allow skipping tuf||sigstore verfication for UNOFFICIAL custom builds
  • [ ] display a note about unsigned UNOFFICIAL custom builds
• [ ] Verify LineageOS ROM downloads with the LineageOS updater android app
  • sigstore-java is not considered production-ready
  • sigstore-js and tuf-js are IIUC

TUF

TUF: The Update Framework

• src: https://github.com/theupdateframework
• web: https://theupdateframework.io/
• https://github.com/topics/tuf
  • https://github.com/engineerd/wasm-to-oci
• spec: https://theupdateframework.github.io/specification/latest/
• https://theupdateframework.github.io/specification/latest/#goals-to-protect-against-specific-attacks
• https://theupdateframework.io/news/
• TUF implementations
  • PyPI has TUF & Sigstore
  • Docker Notary has TUF
  • OCI Container Image repos may or may not support TUF

python-tuf

• src: https://github.com/theupdateframework/python-tuf
• docs: https://github.com/theupdateframework/python-tuf/tree/develop/examples/

  tuf-js

• src: https://github.com/theupdateframework/tuf-js

  go-tuf

• src: https://github.com/theupdateframework/go-tuf

Sigstore

• web: https://sigstore.dev/
• status: https://status.sigstore.dev/
• src: https://github.com/sigstore/
• gh topic: https://github.com/topics/sigstore
  • https://github.com/sigstore/gitsign#what-data-does-gitsign-store
• docs: https://docs.sigstore.dev/
• https://docs.sigstore.dev/#how-to-use-sigstore
• "How to Use Sigstore without Sigstore" (2023) https://eprint.iacr.org/2023/003.pdf

  The CLIs, when used to sign a software artifact, basically run the following procedure: 1) Generate a disposable key pair 2) Obtain a customizable OIDC token (e.g., for a workflow, VM, or Gmail user) 3) Request a public-key certificate from Fulcio using the key pair and the token 4) Digitally sign (the hash of) the software artifact using the private key 5) Timestamp the signature using Rekor 6) Output the certificate, the digital signature from step 4, and the timestamp data from step 5

  Then the authenticity of a software artifact can be verified offline with the following proofs: a) The output from step 6 b) The root certificate of Fulcio c) The public key that Rekor used to sign the timestamp data

  • https://github.com/sigstore/sigstore-python/issues/483

fulcio

• src: https://github.com/sigstore/fulcio

  sigstore OIDC PKI A Free-to-Use CA For Code Signing

  Fulcio is a free-to-use certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity, such as email address.

  Fulcio only issues short-lived certificates that are valid for 10 minutes.

• https://fulcio.sigstore.dev/
• https://fulcio.sigstore.dev/api/v2/trustBundle

rekor

• src: https://github.com/sigstore/rekor

  The Rekor project provides a restful API based server for validation and a transparency log for storage. A CLI application is available to make and verify entries, query the transparency log for inclusion proof, integrity verification of the transparency log or retrieval of entries by either public key or artifact.

cosign

• src: https://github.com/sigstore/cosign

sigstore-js

• src: https://github.com/sigstore/sigstore-js

sigstore-java

• src: https://github.com/sigstore/sigstore-java

sigstore-python

• src: https://github.com/sigstore/sigstore-python
• docs: https://sigstore.github.io/sigstore-python/
• docs: https://sigstore.github.io/sigstore-python/sigstore/sign.html
• docs: https://sigstore.github.io/sigstore-python/sigstore/verify.html
• https://github.com/sigstore/sigstore-python/network/dependents
  • https://github.com/python/release-tools/
  • https://github.com/python/release-tools/blob/8a66d95a3d93af799e5740053478c45eb79d0e70/run_release.py#L738
  • https://github.com/python/release-tools/blob/8a66d95a3d93af799e5740053478c45eb79d0e70/add-to-pydotorg.py#L164 ctrl-f sigstore
  • https://www.python.org/download/sigstore/ :

    python -m pip install -r https://raw.githubusercontent.com/sigstore/sigstore-python/main/install/requirements.txt
    # or, without checking the sha256 checksums in the requirements.txt
    python -m pip install sigstore
    python -m sigstore verify identity \
     --certificate Python-3.11.0.tgz.crt \
     --signature Python-3.11.0.tgz.sig \
     --cert-identity pablogsal@python.org \
     --cert-oidc-issuer https://accounts.google.com \
    Python-3.11.0.tgz

  • https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/building_running_and_managing_containers/assembly_signing-container-images_building-running-and-managing-containers#signing-container-images-with-sigstore-signatures-using-fulcio-and-rekor_assembly_signing-container-images
  • https://github.com/mayaCostantini/sigstore-ansible-github-action
  • https://github.com/sigstore/gh-action-sigstore-python
  • https://github.com/aerleon/aerleon
  • https://aerleon.readthedocs.io/en/latest/install/#verifying-installation
    • SLSA

SLSA

• src: https://github.com/slsa-framework/slsa
• web: https://slsa.dev/
• https://slsa.dev/spec/v1.0/threats-overview
• https://slsa.dev/spec/v1.0/requirements#provenance-generation
• https://slsa.dev/spec/v1.0/provenance#schema
• https://slsa.dev/spec/v1.0/provenance#index-of-build-types
  • https://github.com/nektos/act -- run GH actions {locally, w/ gitea actions,}
• https://github.com/slsa-framework/slsa-github-generator/blob/main/PROVENANCE_FORMAT.md
• https://slsa.dev/spec/v1.0/verifying-artifacts
• https://github.com/slsa-framework/slsa-verifier
• https://github.com/slsa-framework/slsa-verifier#what-is-slsa
• https://github.com/slsa-framework/slsa-github-generator
• https://github.com/slsa-framework/slsa-github-generator#hall-of-fame
• https://security.googleblog.com/2022/04/how-to-slsa-part-2-details.html

[zifnab06]

we provide sha256. we won't be doing anything else.