Hey, I am using Thunderbird + Enigmail using PGP/MIME and I am having an issue verifying my pgp key. If I send an email out that is encrypted and signed to another Email I have setup in thunderbird, everything decrypts and verify's good. It says I have a good signature and email is decrypted fine.
Now If I just sign an email sending the exact same email, Enigmail says that the signature is bad. It even shows that the signature is bad in my "sent folder".
I have experimented a bit and tryed using Inline-PGP instead and It verify's fine using this. Any ideas as to what might be causing this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's strange indeed. Can you attach a debug log file right after you viewed one of the messages with the bad signature? I'd like to see the details that GnuPG issues about the signature.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here is my Log I saved it in this text file attached. I am Using a Protonmail email address with Protonmail Bridge App which I suspect is part of the Issue. It works fine using a different Email Address.
And you're using cubes-gpg-client-wrapper. I'm almost certain that this is not a bug in Enigmail but something in Protonmail. What happens if you save the sent message for Protonmail locally (i.e. not on the Protonmail server)? I bet that the signature is valid then. I'm almost certain that this is not a problem in Enigmail, but somewhere else.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Signature verify's Bad if I save that email locally and check the signature with GPG4USB. I think Protonmail Bridge is creating a bad signature in the email using Thunderbird+Enigmail when It is sent somehow. If I use the same key in GPG4USB and verify some clipboard content with the same key it verifyies correctly. Also If I use Protonmail Web Browser instead of Thunderbird, If I send an email that Is signed using the same Key, the email verify's correctly on the other end. I have contacted Protonmail about this issue to make them aware of it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey, I am using Thunderbird + Enigmail using PGP/MIME and I am having an issue verifying my pgp key. If I send an email out that is encrypted and signed to another Email I have setup in thunderbird, everything decrypts and verify's good. It says I have a good signature and email is decrypted fine.
Now If I just sign an email sending the exact same email, Enigmail says that the signature is bad. It even shows that the signature is bad in my "sent folder".
I have experimented a bit and tryed using Inline-PGP instead and It verify's fine using this. Any ideas as to what might be causing this?
That's strange indeed. Can you attach a debug log file right after you viewed one of the messages with the bad signature? I'd like to see the details that GnuPG issues about the signature.
Here is my Log I saved it in this text file attached. I am Using a Protonmail email address with Protonmail Bridge App which I suspect is part of the Issue. It works fine using a different Email Address.
And you're using cubes-gpg-client-wrapper. I'm almost certain that this is not a bug in Enigmail but something in Protonmail. What happens if you save the sent message for Protonmail locally (i.e. not on the Protonmail server)? I bet that the signature is valid then. I'm almost certain that this is not a problem in Enigmail, but somewhere else.
The Signature verify's Bad if I save that email locally and check the signature with GPG4USB. I think Protonmail Bridge is creating a bad signature in the email using Thunderbird+Enigmail when It is sent somehow. If I use the same key in GPG4USB and verify some clipboard content with the same key it verifyies correctly. Also If I use Protonmail Web Browser instead of Thunderbird, If I send an email that Is signed using the same Key, the email verify's correctly on the other end. I have contacted Protonmail about this issue to make them aware of it.