OpenPGP: unknown signature key algorithm: 22

Marco Nguitragool <[email protected]>
Newsgroups gmane.comp.encryption.bouncy-castle.devel
Message-ID <[email protected]>
Hello everyone,

I cannot read my public key ring, anymore. I get this exception:

|java.io.IOException: unknown signature key algorithm: 22 at org.bouncycastle.bcpg.SignaturePacket.<init>(Unknown Source) ~[bcpg-jdk15on-1.56.jar:1.56.0.0] at org.bouncycastle.bcpg.BCPGInputStream.readPacket(Unknown Source) ~[bcpg-jdk15on-1.56.jar:1.56.0.0] at org.bouncycastle.openpgp.PGPKeyRing.readSignaturesAndTrust(Unknown Source) ~[bcpg-jdk15on-1.56.jar:1.56.0.0] I already upgraded to BouncyCastle 1.59, which AFAIK is the newest, but the problem is still the same. Here is the issue for my project: https://github.com/subshare/subshare/issues/61 Could you please fix this by adding support for this new algorithm? Additionally, I'd like to know when the new file formats used since GnuPGP 2.x are going to be supported. The original idea was to be compatible with GnuPG and use the same key-rings everywhere (in e-mails and subshare), but currently, this is not possible :-( Best regards, Marco :-) |
signature.asc (application/pgp-signature, 801 B)
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJbJkhzAAoJEILFK8lKsPvBcEUP/36ylCwdP8uOjhMzhrocVEgz
o+SggTmX2yya0WuZMq9QNNjxo+3FQtaOnYrPshaHMnS1Ru5J4sUrFiiT0SLhHPwo
qD/d/5iF/M0gZZUT1fUppTePHswHQGn5yvOmIwKhv83HMi6af0b2iGU3oC5X6YSd
Ea9SeUTnaZVsKPi7SI9NKCo/TQ1eDUuY/FYeLJGq4NivYEKPEobDO0MksGf6OSMa
sCJsYtG1Dj6Qr1AZ4up+ii8k6bPswCPyduqBOvF+6LFLna+Wxi+/GWSyAUxsPO8R
9BKYmeNJ6VOnnlK5/9avfCajn5BTEvoapbyojN42SLfphjkHL4Z6Ex5T0vg6AOER
aI+JnjwTMqDS5xmIya0tGcrr+0L8hJg5MZkLFbn1xUAOVEEnPLcT/1Lw/rnJ8HM4
DcKmfPuRLub6NKDROZNWTDQMbcsPifIH+xuzylQ2VFbljmXdOJR2lYIQ8BiuPfK/
//tfaI1NEJsjYkmOwbeirpZdndQ4BC3bNm2oMrNOcUK0lRuwtEAM5uGJ0vIoSc7Z
baVB4CCR0lT78cNS5l/MNBIe/4pOUOKS4cnaPvHgOsPGcqGDChbaXfJ4TpZ8YHXa
CwLk2QPK4vkoPMLTMzdTpWSmE3O+kePj6wN7x9eI6Z3uKr4oBcy5ZeGfJKdM6zYe
GuUrw6rbDQowYkox1th1
=mY6R
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.