Skip to content

Latest commit

 

History

History
103 lines (86 loc) · 3.39 KB

README.md

File metadata and controls

103 lines (86 loc) · 3.39 KB
Raw

signed-container

A signed container example, with cosign.

How It Works

This container image is built and pushed to GitHub Container Registry at ghcr.io/dlorenc/signed-container every time a commit is merged to main. The containers are tagged with the git commit the container was built at. For example: ghcr.io/dlorenc/signed-container:b018f3ffe2474a9c507cbd5320f47651453d4b19 was built at the commit b018f3ffe2474a9c507cbd5320f47651453d4b19.

The public key that can be used to verify each container image is stored right in the git repo, in the file cosign.pub. The private key is also stored right here (encrypted!) in cosign.key. The GitHub action is configured with a secret containing the password for this key (CosignPassword).

Key Rotation

With this flow (committing keys into the repo), rotating keys is as simple as generating and commiting a new key pair. Each build contains a (signed) reference back to the commit (with public key)!

You can verify the entire history by checking out each release tag and verifying the releases against the public keys present in the repo at that time.

Verifying

You can do a simple verification with:

$ cosign verify -key cosign.pub ghcr.io/dlorenc/signed-container:v0.0.2 | jq .
The following checks were performed on these signatures:
  - The cosign claims were validated
  - The signatures were verified against the specified public key
{
  "Critical": {
    "Identity": {
      "docker-reference": ""
    },
    "Image": {
      "Docker-manifest-digest": "sha256:ca4c4567389ae76034040fed221c97bf12e814201f7c0633fde95fe9320ccabc"
    },
    "Type": "cosign container signature"
  },
  "Optional": {
    "git_sha": "6f8e963d1a4185c9e3fa58c39be1e77fdfe3c16d",
    "git_tag": "v0.0.2"
  }
}

This tells you that the container was signed with the private key in this repo.

CI Builds

The continuous CI builds are signed with an extra annotation including the git commit they were built at. This can be verified with:

$ cosign verify -a  git_sha=$(git rev-parse HEAD) -key cosign.pub ghcr.io/dlorenc/signed-container:v0.0.2 | jq .
The following checks were performed on these signatures:
  - The specified annotations were verified.
  - The cosign claims were validated
  - The signatures were verified against the specified public key
{
  "Critical": {
    "Identity": {
      "docker-reference": ""
    },
    "Image": {
      "Docker-manifest-digest": "sha256:ca4c4567389ae76034040fed221c97bf12e814201f7c0633fde95fe9320ccabc"
    },
    "Type": "cosign container signature"
  },
  "Optional": {
    "git_sha": "6f8e963d1a4185c9e3fa58c39be1e77fdfe3c16d"
  }
}

Releases

The release builds are signed with another extra annotation including the git tag (in addition to the commit):

$ cosign verify -a  git_sha=$(git rev-parse v0.0.1) -key cosign.pub ghcr.io/dlorenc/signed-container:v0.0.2 | jq .
The following checks were performed on these signatures:
  - The specified annotations were verified.
  - The cosign claims were validated
  - The signatures were verified against the specified public key
{
  "Critical": {
    "Identity": {
      "docker-reference": ""
    },
    "Image": {
      "Docker-manifest-digest": "sha256:ca4c4567389ae76034040fed221c97bf12e814201f7c0633fde95fe9320ccabc"
    },
    "Type": "cosign container signature"
  },
  "Optional": {
    "git_sha": "6f8e963d1a4185c9e3fa58c39be1e77fdfe3c16d",
    "git_tag": "v0.0.2"
  }
}