Skip to content

rekor: Use checkpoint_key_id when possible #1364

Open
@jku

Description

@jku

Description

sigstore/protobuf-specs#629

It seems when we lookup correct keys in trust root, we should use checkpoint_key_id if it is available and log_id only as fallback.

Changes:

  • the rekor keyring is currently essentially a dict[keyid, PublicKey]: we need to track checkpoint_key_id as well -- I'm guessing it makes sense to store the whole RekorLog in the container, not just PublicKey
  • the checkpoint code currently calls RekorKeyring.verify() with a keyid argument: this needs to be redesigned a bit

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions