On 2016-10-04 07:09, cubit wrote:
I am using an older version of Enigmail as during the time Split GPG and enigmail did not seem to work well together. Enigmail expecting gpg2 while split gpg on qubes was offering gpg1.
If I want to upgrade my enigmail to the latest is there anything I need to do to the split GPG set up or should it all just talk GPG2 now?
Yes, Qubes Split GPG uses gpg2 by default in the backend now.
I upgraded enigmail to v 1.9.5 and it did not go as well as planned. From what I read of the qubes documents there were nothing to change in qubes settings to take into account the GnuPG2 requrement now.
But when I run thunderbird 45.2.0 + enigmail 1.9.5 I get the following error.
" GnuPG reported an error in the communication with gpg-agent (a component of GnuPG).
This is a system setup or configuration error that prevents Enigmail from working properly and cannot be fixed automatically.
We strongly recommend that you consult our support web site at https://enigmail.net/faq."
The messages decrypt but I lose the notification that the email was decrypted and I do not see any of the options to view details of the encrypted message such like who it was encrypted for. I did restart both the appVM for thunderbird and the appVM for my keys, both debian 8
I upgraded enigmail to v 1.9.5 and it did not go as well as planned. From what I read of the qubes documents there were nothing to change in qubes settings to take into account the GnuPG2 requrement now.
But when I run thunderbird 45.2.0 + enigmail 1.9.5 I get the following error.
" GnuPG reported an error in the communication with gpg-agent (a component of GnuPG).
This is a system setup or configuration error that prevents Enigmail from working properly and cannot be fixed automatically.
We strongly recommend that you consult our support web site at https://enigmail.net/faq."
The messages decrypt but I lose the notification that the email was decrypted and I do not see any of the options to view details of the encrypted message such like who it was encrypted for. I did restart both the appVM for thunderbird and the appVM for my keys, both debian 8
Hello qubers,
Has anyone experienced problems with using Splig GPG with Thunderbird and Enigmail 1.9.5 in Debian 8 appVM? Have also tried to build the AppVM and TB install from scratch instead of simpli upgrading enigmail with existing AppVM. When ever I try I get the above error. when checking encrypted email.
Cubit
Has anyone experienced problems with using Splig GPG with Thunderbird and Enigmail 1.9.5 in Debian 8 appVM? Have also tried to build the AppVM and TB install from scratch instead of simpli upgrading enigmail with existing AppVM. When ever I try I get the above error. when checking encrypted email.
Sorry for bumping but hoping someone knows a solution for this?
Hi,
What template are you using for the gpg VM?
As far as I can tell, gpg2 always requires access to gpg-agent, even if your keys have no passphrase. I realized this was the problem when running "echo test | gpg2 -v --clearsign" in a terminal in the gpg VM always failed. Switching from a modified fedora23-minimal to a full fedora23 template solved the problem for me. If you're also using a debian-8 template for the gpg VM, it might be missing the same thing that fedora23-minimal was missing. (Which I never figured out because I needed to get enigmail working.)
Best,
Daniel
On Wednesday, November 16, 2016 at 10:21:33 PM UTC-5, george wrote:
Yes. I get the same issue too. I can read the message, but I can't write, and I'm also in Debian-8 VM on Qubes 3.2, with Enigmail and Thunderbird. I can READ messages, but I can't send them, nor verify/encrypt/sign them. I'm not sure what to do with this...
What template are you using for the gpg VM?
For me both my vault VM and thunderbird VM are sharing the same Debian 8 template. This template does have gnupg-agent 2.0.26-6+deb8u1 installed