Error: rnp_key_valid_till64 failed on ELG encrypted message
I received an encrypted email which octopus cannot decrypt.
This is the thundebird output when trying to opening the email:
2023-10-05 07:29:27.975007790 UTC: sequoia-octopus: rnp_op_verify_execute: failed to decrypt: No key to decrypt message
2023-10-05 07:29:28.020457143 UTC: sequoia-octopus: rnp_key_valid_till64: parameter "key" is null
console.log: "CryptoAPI.sync() failed result: %o" (new Error("rnp_key_valid_till64 failed", "chrome://openpgp/content/modules/RNP.jsm", 1220))
JavaScript error: chrome://openpgp/content/modules/RNP.jsm, line 1220: Error: rnp_key_valid_till64 failed
But decryption with gpg --decrypt msg.asc
works fine.
Here is the output when decrypting the email with gpg, private data of third parties XXXed out:
gpg --decrypt msg.asc
gpg: encrypted with 2048-bit ELG key, ID XXX, created XXX
"XXX"
gpg: encrypted with 255-bit ECDH key, ID 695199C1239445F2, created 2023-02-07
"CCC Mitgliederverwaltung (Key 2023) <mitgliedschaft@ccc.de>"
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
XXX
gpg: Signature made XXX
gpg: using DSA key XXX
gpg: Good signature from "XXX" [undefined]
gpg: aka "XXX" [undefined]
gpg: aka "XXX" [undefined]
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: XXX
My guess would be that the unsupported ELG encryption throws sequoia off instead of continuing on with the supported encryption?