Skip to content

current release fails hard if trusted root contains ed25519 #1423

@jku

Description

@jku
  • root-signing-staging is trying to add a ed25519 key into trusted root
  • sigstore-python main branch already supports this key type
  • current sigstore-python release unfortunately fails hard: if the trusted root contains an unrecognised keytype the verification fails even if the key is not needed to verify

The specific failure is easy to fix and I think I'd like to fix this is as a point release from a 3.6.x branch: There are a lot of changes in main since last release that are not really useful before rekor v2 support is fully integrated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions