GPGMail, “Encrypt messages by default”, not working if “Send again” is used
Hi, thanks for making the GPG suite. It’s awesome! :)
Here is on bug I encountered in GPGMail version 2.5b5:
If you use “Send again” Mail or GPGMail won’t
honour the “Encrypt messages by default” option.
Short story:
I have the “Encrypt messages by default” option on, so
every time I create a mail to certain addresses the mail
automatically gets encrypted. Recently I wanted to add something to
a mail already sent. So I hit the “Send again” button,
changed the text and sent the corrected mail again. The problem
was: that second mail did not get encrypted.
Since I use the “Encrypt messages by default” option I
did not check if the encrypt button was on. Also the first e-mail
was encrypted, so I did not expect that the second edited message
would not get encrypted.
I think this behaviour should be changed (bug should be fixed) since it will lead users to accidentally not encrypt messages.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Steve on 10 Feb, 2015 11:19 AM
Hi Paul,
it is indeed a bug and qualifies for a high priority bug, since it poses a real security threat.
We've a ticket for this problem and I have connected it with this discussion so that if this discussion get's closed, it will be re-opened as soon as the ticket is closed so you'll receive a notification. Feel free to open a new discussions should you run into further problems or need assistance.
Thanks for letting us know and taking the time to report this.
All the best,
steve
Support Staff 2 Posted by Steve on 12 Feb, 2015 09:04 PM
Hi Paul,
this issue has been fixed. If you want to test the fix, please download our latest nightly GPG Suite. That page also has sig and SHA1 to verify the download.
Should the problem persist, please re-open this discussion. If you have other questions you can open a new one any time.
Best, steve
Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.
Steve closed this discussion on 12 Feb, 2015 09:04 PM.
paul re-opened this discussion on 13 Feb, 2015 06:38 PM
3 Posted by paul on 13 Feb, 2015 06:38 PM
Hi Steve,
I have tried it and it works great.
Thank you!
Paul
Support Staff 4 Posted by Steve on 15 Feb, 2015 09:20 PM
Perfect. I'm closing this discussion. If you need further assistance or have questions you can re-open this discussion here or open a new one any time.
Best, steve
Steve closed this discussion on 15 Feb, 2015 09:20 PM.