Commits on Nov 19, 2021

1. Add flag for manually specifying a hash algo when verifying …

   While, at the time of writing, it's not possible to manually specify the
   signature digest algorithm which should be used when signing an image,
   some KMS providers have key types which force a digest algorithm which
   isn't sha256; e.g. GCP KMS with RSA4096 / SHA512 keys.
   
   Cosign will happily use these keys for signing and will infer the digest
   algorithm based on what the KMS provider mandates, leading to a
   situation where cosign generates signatures it can't verify.
   
   This commit adds a new flag which allows the user to manually specify
   one of 4 commonly-used secure hashes when using `cosign verify`
   
   Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>

   

   SgtCoDFish committed Nov 19, 2021
   Configuration menu

   • View commit details
   • Copy full SHA for bc75f0e
   • Browse repository at this point

   Copy the full SHA

   bc75f0e View commit details

   Browse the repository at this point in the history