Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Signed but not encrypted messages are marked "invalid digital signature"

more options

When receiving signed but not encrypted messages, thunderbird complains with "invalid digital signature" and "technical error deteced". Unpacking the message and checking with gpg manualy verifies the signature correctly. Messages encrypted and signed are verified correctly. When looking at the logs in the console, I can see:


<< ----

openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14 openpgp: Decrypting message: -----BEGIN PGP SIGNATURE----- ..[snipped]


END PGP SIGNATURE-----

decryption.sys.mjs:143:14 openpgp: Nothing to decrypt/verify. decryption.sys.mjs:176:16 openpgp: Decrypting message: -----BEGIN PGP SIGNATURE----- ..[snipped]


END PGP SIGNATURE-----

decryption.sys.mjs:143:14 openpgp: Nothing to decrypt/verify. decryption.sys.mjs:176:16 openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14 openpgp: Found signed MIME message; micalg=pgp-sha256 mimeVerify.sys.mjs:148:16 openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14 openpgp: Found signed MIME message; micalg=pgp-sha256


>>----

Does simply singing without encryption require some special settings?

When receiving signed but not encrypted messages, thunderbird complains with "invalid digital signature" and "technical error deteced". Unpacking the message and checking with gpg manualy verifies the signature correctly. Messages encrypted and signed are verified correctly. When looking at the logs in the console, I can see: ----<< ---- openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14 openpgp: Decrypting message: -----BEGIN PGP SIGNATURE----- ..[snipped] -----END PGP SIGNATURE----- decryption.sys.mjs:143:14 openpgp: Nothing to decrypt/verify. decryption.sys.mjs:176:16 openpgp: Decrypting message: -----BEGIN PGP SIGNATURE----- ..[snipped] -----END PGP SIGNATURE----- decryption.sys.mjs:143:14 openpgp: Nothing to decrypt/verify. decryption.sys.mjs:176:16 openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14 openpgp: Found signed MIME message; micalg=pgp-sha256 mimeVerify.sys.mjs:148:16 openpgp: Parsed contentTypeLine: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------95ynGFLP1eI6rMalg5HH0Iop" mimeVerify.sys.mjs:133:14 openpgp: Found signed MIME message; micalg=pgp-sha256 ---- >>---- Does simply singing without encryption require some special settings?

Vsi odgovori (2)

more options

I try not to follow PGP. But I am aware various libraries supports all sort of broken and obsolete signature files that the library in Thunderbird does not.

Have you considered posting your request in the encryption list where those that have an interest can be found as discussed in the end to end encryption user documentation https://support.mozilla.org/en-US/kb/introduction-to-e2e-encryption#w_discussion-and-support.?

more options

Hm, looks more like a TB than GPG issue to me. Anyway, opend a new issue at https://thunderbird.topicbox.com/groups/e2ee . Thanks.