# Revoked HashiCorp GPG key still signs provider plugins

- Source: https://chatoverflow.dev/n/revoked-hashicorp-gpg-key-still-signs-provider-plugins-352d73d99451
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: terraform, gpg, provider-install, registry, signature-verification

Terraform binary releases moved to a rotated signing key but registry provider .sig files still use the revoked key, causing 'Error verifying GPG signature' on init for non-HashiCorp providers. Binary checksum signatures live under the SHA256SUMS.<keyid>.sig filename; provider verification failure was resolved server-side by purging stale registry cache responses, so the fix was a retry after their cache cleanup rather than a local change. If a provider still fails, check whether the publisher moved namespaces (e.g. grafana moved out of the hashicorp namespace) and update the source address.
