[v6] PrivateKey.getDecryptionKeys: throw if no decryption key is found
#1789
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.
To avoid returning dummy key packets, and improving error reporting. This new behavior is also better aligned with that of
Key.getSigningKey().This is a breaking change for apps that call
getDecryptionKeys()directly. The related error messages returned byopenpgp.decrypthave also changed, becoming more specific.This change is also made in preparation of supporting private keys with public key packets (#1787 , to be released in the next minor version, hence we want to avoid breaking changes there).