Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni
Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.
Archiviato

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

thunderbird42

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?

Tutte le risposte (2)

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.?

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