Beta doesn't decrypt
I've been trying out the beta, and along with the "expired" bug, I have a problem - it doesn't decrypt. To decrypt email that's been sent to me, I have to cut and paste it into a text editor, and manually decrypt it.
I understand that it's the first beta, no real need to respond to this - just letting you guys know the experience that I'm having.
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
1 Posted by slammingrooves on 07 Nov, 2014 07:22 PM
Ok, now I've received a decrypted email...but it never asked me to put in my password. So I guess I still had a session open?
It seems like things that come before I enter my password are being ignored. Things that come afterwards are properly decrypted..
Support Staff 2 Posted by Steve on 07 Nov, 2014 09:01 PM
Hi,
as for the expired bug, we are investigating that and hope to have a fix ready soon.
Did you restart your machine? A mail.app restart will indeed help workaround the expired bug, until we have a fix. But a system restart might help as well.
If mails do not get decrypted, there's something else going on.
Could you try finding an exact workflow to reproduce the not decrypted mail problem?
If that happens again, also open console.app and see if it spits any related GPGMail / gpg / Libmacgpg errors.
All the best,
steve
3 Posted by slammingrooves on 08 Nov, 2014 05:17 PM
Ok, here's how it went:
At that point, the email was still encrypted, so I cut and pasted the contents into a text editor, selected all, and used the key combination that decrypts, and at that point the text decrypted, and I was able to read it.
I then replied to his email, again encrypted, and he replied with another encrypted email. This time I was not prompted for a password (I'm assuming there's a session that's open for a certain amount of time when I enter the password, and that session had not expired yet), and I was able to read the email.
I confirmed that that email had been encrypted by checking it from the gmail web portal, so that email was successfully decrypted.
4 Posted by cliff1976 on 08 Nov, 2014 07:06 PM
Do you know whether the method of mail composition your buddy used was PGP/MIME or inline PGP code? If the latter, it sounds like the same issue reported here.
Support Staff 5 Posted by Steve on 10 Nov, 2014 09:33 PM
Hi everybody,
we'd like to apologize again for this annoyance.
We've managed to fix this really stupid bug and have a new test build for you.
It would be great if some of you could install the new build and let us know if this fixes the problem as it should.
To test, please follow these steps:
1.) Download the new GPGMail version:
https://releases.gpgtools.org/GPGMail-2.5b1-790.dmg
GPG Signature can be found at: https://releases.gpgtools.org/GPGMail-2.5b1-790.dmg.sig
2.) Simply run the installer (no need to uninstall it first)
(Should you have uninstalled GPG Suite in the meantime, please re-run the Yosemite-Beta1 installer and after that, install this new GPGMail version)
3.) Open Mail.app -> Preferences -> GPGMail and make sure you're seeing build 790b
4.) Let us know if everything works as expected now
Thanks!
6 Posted by cliff1976 on 11 Nov, 2014 06:26 PM
2.5b1 build 790b fixed this issue for me!
Thanks,
Cliff
Support Staff 7 Posted by Steve on 13 Dec, 2014 11:27 PM
Perfect. Glad, this is solved for you. 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 13 Dec, 2014 11:27 PM.