Re: [Enigmail] difference in output between 1.4.x and 2.0.x when agent fails to sign -- causes enigmail to send broken messages

2014-11-11 Thread Werner Koch
On Mon, 10 Nov 2014 21:52, d...@fifthhorseman.net said: I believe this is two distinct issues, and maybe we want to address them both: * gnupg 2.1.x might want to buffer data before the signature is made, and decline to emit anything if the signature fails There is a lot of buffering

Re: [Enigmail] difference in output between 1.4.x and 2.0.x when agent fails to sign -- causes enigmail to send broken messages

2014-11-11 Thread Ludwig Hügelschäfer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10.11.14 23:12, Daniel Kahn Gillmor wrote: Can you try with enigmail 1.7.2? I'd like to know if this is a bug due to the choice of platform (i.e. if we need to do something different on Linux than on Mac). Same result with 1.7.2 (and gnupg

Re: [Enigmail] difference in output between 1.4.x and 2.0.x when agent fails to sign -- causes enigmail to send broken messages

2014-11-10 Thread Daniel Kahn Gillmor
On 11/10/2014 11:51 AM, Ludwig Hügelschäfer wrote: On 10.11.14 22:46, Daniel Kahn Gillmor wrote: I'm not seeing either of these alerts when sending encrypted+signed messages with PGP/MIME using enigmail 1.7.2 and gnupg 2.1.0 on debian GNU/Linux, x86_64 (amd64) platform. Are you sure