-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/20/16 03:41, Marek Marczykowski-Górecki wrote:
> On Sat, Nov 19, 2016 at 09:11:21PM -0800, Andrew David Wong wrote:
>> On 2016-11-19 03:43, Andrew David Wong wrote:
>>> On 2016-11-17 10:05, cubit wrote:
17. Nov 2016 15:33 by
Marek Marczykowski-Górecki:
> On Sat, Nov 19, 2016 at 09:11:21PM -0800, Andrew David Wong wrote:
>> On 2016-11-19 03:43, Andrew David Wong wrote:
>>> On 2016-11-17 10:05, cubit wrote:
17. Nov 2016 15:33 by dmoer...@gmail.com:
>>>
> On Wednesday, November 16, 2016 at 10:21:33 PM UTC-5,
Marek Marczykowski-Górecki:
> On Sat, Nov 19, 2016 at 09:11:21PM -0800, Andrew David Wong wrote:
>> On 2016-11-19 03:43, Andrew David Wong wrote:
>>> On 2016-11-17 10:05, cubit wrote:
17. Nov 2016 15:33 by dmoer...@gmail.com:
>>>
> On Wednesday, November 16, 2016 at 10:21:33 PM UTC-5,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, Nov 19, 2016 at 09:11:21PM -0800, Andrew David Wong wrote:
> On 2016-11-19 03:43, Andrew David Wong wrote:
> > On 2016-11-17 10:05, cubit wrote:
> >> 17. Nov 2016 15:33 by dmoer...@gmail.com:
> >
> >>> On Wednesday, November 16, 2016 at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-11-19 03:43, Andrew David Wong wrote:
> On 2016-11-17 10:05, cubit wrote:
>> 17. Nov 2016 15:33 by dmoer...@gmail.com:
>
>>> On Wednesday, November 16, 2016 at 10:21:33 PM UTC-5, george wrote:
Yes. I get the same issue too. I can read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/19/2016 06:43 AM, Andrew David Wong wrote:
> Sorry, this is a known issue. Enigmail 1.9 is incompatible with
> Split GPG on Debian 8:
>
> https://github.com/QubesOS/qubes-issues/issues/2170
>
> Until this is resolved, I recommend using the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-11-17 10:05, cubit wrote:
> 17. Nov 2016 15:33 by dmoer...@gmail.com:
>
>> 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
17. Nov 2016 15:33 by dmoer...@gmail.com:
> 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
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.
On Sunday, October 9, 2016 at 11:17:53 AM UTC-4, cubit wrote:
> 4. Oct 2016 19:40 by cu...@tutanota.com:
> 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
9. Oct 2016 15:17 by cu...@tutanota.com:
>
> 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
4. Oct 2016 19:40 by cu...@tutanota.com:
>
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-10-04 07:09, cubit wrote:
> Hello
>
> 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
Hello
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
14 matches
Mail list logo
