Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Docs: PGP & gpg version requirements with ECDH & Vault 1.13.x or higher into release/1.17.x #27777

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #27767 to be assessed for backporting due to the inclusion of the label backport/1.17.x.

The below text is copied from the body of the original PR.


Added notes in Developer / Vault / Documentation / Concepts / PGP, GnuPG, and Keybase regarding GnuGPG versions 2.2.21 or higher being required where padding differences with ECDH keys used in Vault versions 1.12.x or earlier work with older GPG versions but newer Vault versions encounter the generic error: gpg: decryption failed: No secret key

Fixes #25965

Screenshot 2024-07-11 at 21 49 03
Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/docs/pgp-gpg-versions/constantly-fluent-polliwog branch from b53e7b2 to e03ca1e Compare July 15, 2024 13:31
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 15, 2024
Copy link

CI Results:
All Go tests succeeded! ✅

Copy link

Build Results:
All builds succeeded! ✅

@schavis schavis merged commit d986e78 into release/1.17.x Jul 15, 2024
28 of 30 checks passed
@schavis schavis deleted the backport/docs/pgp-gpg-versions/constantly-fluent-polliwog branch July 15, 2024 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants