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
It seems that cr-gpg makes the signature on the message before gmail reflows long lines. In an email I sent, I got a bad signature that became good again when I checked it with gpg after removing the newlines that gmail inserted.
I don't know what would be a nice solution to this - implementing a reflowing algorithm similar to gmail's is subject to errors and to changes in gmail, but asking the user to format the email by himself is also burdensome. Maybe a warning for long lines (>72 char) would be a good starting point...
The text was updated successfully, but these errors were encountered:
Hi Stefano
Yeah this is a tricky issue since as you mentioned you cant really change a persons email. I do have a idea how it could be solved thanks to some of the work that was done recently for detached sig verification.
If it possible to send me a example of a mail that would fail verification so that I can confirm if my fixes work or not. My contact address is jameel at thinkst dot com
Thinking about it, maybe the best sub-optimal solution to me is implementing a "Reflow" button that does it (plus warning for long lines) - but it has to be manual, not automatic.
It seems that cr-gpg makes the signature on the message before gmail reflows long lines. In an email I sent, I got a bad signature that became good again when I checked it with gpg after removing the newlines that gmail inserted.
I don't know what would be a nice solution to this - implementing a reflowing algorithm similar to gmail's is subject to errors and to changes in gmail, but asking the user to format the email by himself is also burdensome. Maybe a warning for long lines (>72 char) would be a good starting point...
The text was updated successfully, but these errors were encountered: