Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Patrick Brunschwig
Mark Rousell wrote on 08.10.2019 16:57: [...] > Whilst OpenPGP support should ideally of course have been built into > Thunderbird from the beginning (alongside S/MIME support) I have to say > that, as things now stand, I have more confidence in the development and > project management of Enigmail

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Dmitry Alexandrov
"Hernâni Marques (p≡p foundation)" wrote: > On 08.10.19 18:37, Dmitry Alexandrov wrote: > >> Pity, but I hope it will be better that way. In particular I hope, that >> Mozilla will not follow your example and won’t entice users to proprietary >> isolated keyserver [0] instead of distributed

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Phil Stracchino
On 10/8/19 12:41 PM, Robert J. Hansen wrote: >> I have a terrible feeling that as with Firefox, this change in >> Thunderbird is going to carpet-nuke Thunderbird's add-on ecosystem and >> severely reduce its overall utility. WebExtensions has been around >> since 2015 and the Firefox

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Eli Schwartz
On 10/8/19 12:49 PM, Robert J. Hansen wrote: >> In particular I hope, that Mozilla will not follow your example and >> won’t entice users to proprietary isolated keyserver [0] > > The Hagrid codebase is not proprietary. It's been fully open sourced > and is developed by the same people behind

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread p≡p foundation
On 08.10.19 18:49, Robert J. Hansen wrote: > The Hagrid codebase is not proprietary. It's been fully open sourced > and is developed by the same people behind the open-source SequoiaPGP. Which is financed 100% by pEp (including the initial work on Hagrid) -- even if we reject keyservers

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread p≡p foundation
On 08.10.19 18:37, Dmitry Alexandrov wrote: > Pity, but I hope it will be better that way. In particular I hope, that > Mozilla will not follow your example and won’t entice users to proprietary > isolated keyserver [0] instead of distributed SKS network thus splitting the > keybase. And

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Robert J. Hansen
> In particular I hope, that Mozilla will not follow your example and > won’t entice users to proprietary isolated keyserver [0] The Hagrid codebase is not proprietary. It's been fully open sourced and is developed by the same people behind the open-source SequoiaPGP. I understand you don't

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Phil Stracchino
On 10/8/19 10:57 AM, Mark Rousell wrote: > On 08/10/2019 08:08, Patrick Brunschwig wrote: >> The Thunderbird developers have announced that they will implement >> OpenPGP support in Thunderbird 78 [1]. Support for Thunderbird in >> Enigmail will therefore be discontinued. > > Wow. > > Patrick,

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Robert J. Hansen
> Patrick, first of all I'd like to thank you for all the effort you have > put into Enigmail (and will continue to put into it). Without your > brilliant work it is clear that Thunderbird would not have been as > successful as it has been. Absolutely. Hear, hear. :) > Whilst OpenPGP support

Re: [Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Mark Rousell
On 08/10/2019 08:08, Patrick Brunschwig wrote: > The Thunderbird developers have announced that they will implement > OpenPGP support in Thunderbird 78 [1]. Support for Thunderbird in > Enigmail will therefore be discontinued. Wow. Patrick, first of all I'd like to thank you for all the effort

[Enigmail] Future OpenPGP Support in Thunderbird

2019-10-08 Thread Patrick Brunschwig
The Thunderbird developers have announced that they will implement OpenPGP support in Thunderbird 78 [1]. Support for Thunderbird in Enigmail will therefore be discontinued. I'd like to explain in the following paragraphs what this will mean for Enigmail, and why this is an inevitable step. The