Backport of Docs: PGP & gpg version requirements with ECDH & Vault 1.13.x or higher into release/1.17.x #27777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Overview of commits