-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#5458 Improve parsing of pgp/mime message with attachment #5518
Conversation
@martgil this one ready for review, thanks! |
@sosnovsky does the above email from the screenshot available to our |
Yes, it's in |
Got it - thank you, Roma. |
By the way, original message was created using FES 2023-11, the same message from FES 2023-12 doesn't have such issue. Also it happens only in Gmail inbox, while in FlowCrypt Encrypted Inbox message is rendered correctly even without current fix. |
Okay, I did try to create a test email, but I think it is difficult to do so. The issue is, it must be long enough to trigger Gmail's email body message clipping. This means that the non-encrypted data would include large characters, which the browser extension cannot handle, making it difficult to create a test email. That would be a different story since the above screenshot results in a decryption error (probably because it was an encrypted email for another key). I have tested it and it should work on other instances wherein the decrypted content is not very long but the ASCII armored is long enough to trigger Gmail's email body message clipping feature. |
This PR fixes parsing of large PGP/MIME encrypted messages with attachment, which previously were not detected as encrypted ones.
close #5458
before (original message isn't detected as encrypted and rendered as plain text):
after (encrypted message is parsed and correctly renders decryption error):
Tests (delete all except exactly one):
To be filled by reviewers
I have reviewed that this PR... (tick whichever items you personally focused on during this review):