-
Notifications
You must be signed in to change notification settings - Fork 561
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
unknown PGP public key algorithm encountered (EDDSA?) #73
Comments
If I use
So it definitely looks like a broken packet. It would be nice if there were a graceful way to handle this, though... |
Hmmm, I'm getting the same problem for 0x4F0540D577F95F95 which also hits algorithm 22. |
Looks like algorithm 22 is EDDSA. open-keychain/open-keychain#1279 |
Latest draft that I can find: https://tools.ietf.org/html/draft-koch-eddsa-for-openpgp-04 |
FWIW, this is an example file downloaded from a pgp keyserver which illustrates this problem: |
Latest draft spec for this: https://tools.ietf.org/html/draft-ietf-openpgp-rfc4880bis-07 |
I'm am interacting with Passbolt's API and they cloud server key is apparently also Are there plans to include that algorithm? |
Latest draft spec: https://tools.ietf.org/html/draft-ietf-openpgp-rfc4880bis-09 @stoyandimov I have not heard anything. |
I'm working on adding logic to MimeKit to automatically fetch keys from a keyserver and import them when verifying signatures if an unknown key id is encountered (assuming MimeKit is configured to auto-fetch them).
I keep getting an exception about an unknown PGP public key algorithm when trying to read the returned stream. I modified my local copy of BouncyCastle to include the algorithm id in the IOException that gets thrown and the algorithm tag is
22
which doesn't have a mapping in thePublicKeyAlgorithmTag
enum.I took a quick look at rfc4880 and there does not appear to be an algorithm id of 22.
The following test case illustrates the problem.
Test Case:
Error:
The text was updated successfully, but these errors were encountered: