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

OpenPGP flaw with Drafts #1363

Open
c-geek opened this Issue Mar 10, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@c-geek
Copy link

c-geek commented Mar 10, 2017

RainLoop version, browser, OS:
1.10.5.192, Chromium, Ubuntu 16.04

Expected behavior and actual behavior:
When typing a mail that aims to be encrypted using PGP, PLEASE DO NOT SAVE THE DRAFT IN CLEAR. This is an obvious flaw: I am writing encrypted e-mails so only me and my recipient know the content. But if the server saves the draft in clear, well ... we can be more than 2 to know this content: the e-mail provider will be a third.

Steps to reproduce the problem:
Type a mail. The draft will be saved on the server (I'm using IMAP), in clear text.

Logs or screenshots:

@c-geek

This comment has been minimized.

Copy link
Author

c-geek commented Mar 10, 2017

Note: sorry for the caps, I just want to insist on this problem.

I am very happy to benefit from RainLoop and want to use it. If you have a Ğ1 account, I would be very happy to send you some money as a thank.

@unic0rn

This comment has been minimized.

Copy link

unic0rn commented Mar 29, 2017

RainLoop has no way of knowing that you're willing to encrypt the message. as a workaround, does disabling the drafts folder help?

in the long run, perhaps redesigning the pgp UI would be a good choice - some obvious toggle buttons to sign and encrypt (that's one thing that milepile does right, imho), where encrypt button would disable storing the draft on the server, and both would take action after clickling send, not immediately.

@c-geek

This comment has been minimized.

Copy link
Author

c-geek commented Mar 29, 2017

Yes to all what you've said.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment