On Tue 2018-10-02 14:31:13 -0500, Daniel Kahn Gillmor wrote: > I'm now working on figuring out what updates are needed to GnuPG in > debian stable (stretch) to be able to get the enigmail test suite to > pass. Hopefully they'll be minor, and comprehensible.
Turns out there were a half-dozen upstream GnuPG changes that needed backporting to stretch to make the enigmail test suite pass. Additionally, the Enigmail test suite itself needs a bit of cleanup to deal sensibly with the older version of GnuPG (in particular, rapidly setting up and tearing down ephemeral GnuPG homedirs during the test suite causes problems for the older version of gpg-agent, reported upstream as https://gitlab.com/enigmail/enigmail/merge_requests/30) I've requested for the release team to consider the changes for GnuPG in stretch here: https://bugs.debian.org/910398 If the security team (or other people interested in enigmail) want to follow up on that report, i'd appreciate it. In the meantime, for enigmail, i've pushed a debian/stretch branch into salsa with commit id b6e978d64af1defdfed876b09c8a57acb796ad72 as 2:2.0.8-5~deb9u1, which i've tested against the proposed gnupg2 2.1.18-8~deb9u3. I welcome review of both of the GnuPG and Enigmail branches. --dkg
signature.asc
Description: PGP signature