Open jstedfast opened 7 years ago
If I use gpg --export 24ECFF5AFF68370A | gpg --list-packets
, I get:
:public sub key packet:
version 4, algo 22, created 1415374702, expires 0
unknown algorithm 22
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. https://github.com/open-keychain/open-keychain/issues/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 EDDSA
. This makes it veeery difficult for me to work with BouncyCastle.
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: