On 2/4/15 1:21 PM, Ludwig Hügelschäfer wrote:
On 04.02.15 21:21, Doug Barton wrote:
On 2/4/15 9:13 AM, Patrick Brunschwig wrote:
We recently discussed in (a part of) the Enigmail team that we
should think about giving up support for GnuPG 1.4.x.
Reasons: * GnuPG 2.0 was released in November 2006; it has proven
for a long time to be stable. * While GnuPG 1.4 still makes sense
on embedded devices and computers with limited resources, this
does not hold anymore for today's PCs. * We still have quite a
lot of GnuPG 1.4-specific code, and maintenance of Enigmail is
more complex with more versions of GnuPG (e.g. password handling
/ bug 287).
My knee-jerk reaction is that we're not yet at the point where 1.x
usage has dropped sufficiently to warrant this change,
There may have been some misunderstanding.
Nope, I understood the timeline perfectly. :) There are still a lot of
Linux distros that use 1.x by default, and that is not going to change
any time in the next several years.
but before I cast a "No" vote (for whatever that's worth) I'm
curious as to how much more complex development efforts are due to
the 1.x code?
Passphrase handling in Enigmail itself - necessary for gnupg 1.4 - is
a provisional solution and has a hard to catch and ugly bug
(https://sourceforge.net/p/enigmail/bugs/287/)
Doesn't actually answer my question. :) Put a different way, what
percentage of Enigmail developer time is spent addressing issues that
only affect GnuPG 1.x? And perhaps more importantly, what is the
opportunity cost of leaving the code in? What good/new/exciting things
will not be able to happen if the 1.x code is not removed?
Doug
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
