You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When verifying the signature in react, following error is thrown:
Error: boolResponse: signature error: openpgp: unsupported feature: unknown critical signature subpacket type 33
To make sure the signature itself is indeed correct, I imported the pubKey to my gpg keychain and verified the signature via gpg --verify which yields a good result
In react, I use the following to sign and verify: const signature = await OpenPGP.sign(message, publicKey, privateKey, '')
$ gpg --verify message.txt.asc
gpg: assuming signed data in 'message.txt'
gpg: Signature made Thu 17 Mar 15:29:06 2022 CET
gpg: using RSA key C27398C441AC4B6504480280C2D7AF42E056984D
gpg: Good signature from "" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: C273 98C4 41AC 4B65 0448 0280 C2D7 AF42 E056 984D
The text was updated successfully, but these errors were encountered:
I encountered an error on iOS (at least 14.5)
I am trying to verify a signature of following message (IBAN is a fake number I got from here )
{"id":"sepa-IE29AIBK93115212345678","type":"sepa","iban":"IE29 AIBK 9311 5212 3456 78","beneficiary":"Czino"}
Signature is the following
And the corresponding public key
When verifying the signature in react, following error is thrown:
Error: boolResponse: signature error: openpgp: unsupported feature: unknown critical signature subpacket type 33
To make sure the signature itself is indeed correct, I imported the pubKey to my gpg keychain and verified the signature via
gpg --verify
which yields a good resultIn react, I use the following to sign and verify:
const signature = await OpenPGP.sign(message, publicKey, privateKey, '')
and
await OpenPGP.verify(signature, message, publicKey)
The text was updated successfully, but these errors were encountered: