Unfortunately, in order to do that we needed to make some assumptions about the naming of the signature file (as noted in https://github.com/asdf-community/asdf-hashicorp/pull/27). Even more unfortunately, it turns out that those assumptions are not always accurate - specifically, in the latest version of Vault the signature file lacks the key suffix.
This reverts all gpg verification changes for now to unblock users while we figure out the correct implementation for this feature.
https://github.com/asdf-community/asdf-hashicorp/pull/24 added gpg verification to ensure that binaries downloaded by this plugin have not been compromised. Yay!
Unfortunately, in order to do that we needed to make some assumptions about the naming of the signature file (as noted in https://github.com/asdf-community/asdf-hashicorp/pull/27). Even more unfortunately, it turns out that those assumptions are not always accurate - specifically, in the latest version of Vault the signature file lacks the key suffix.
This reverts all gpg verification changes for now to unblock users while we figure out the correct implementation for this feature.