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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11.11.14 22:39, Ludwig Hügelschäfer wrote: > No unsent mail, Should read: No sent mail. Sorry. Ludwig -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJUYoLwAAoJEA52XAUJWdLjgmIH/1lFsql4m/HLEZNbE+b+FmlA arEN04u2YBibgIMn1b4z5qG7XUqx

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

-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 gnup

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

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 bufferin

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10.11.14 23:12, Daniel Kahn Gillmor wrote: > What version of GnuPG are you using? 2.1, thanks to Patrick :-) > 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

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

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

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 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 you'r

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

Thanks for the prompt response, Ludwig! On 11/10/2014 11:25 AM, Ludwig Hügelschäfer wrote: > On 10.11.14 21:52, Daniel Kahn Gillmor wrote: >> * enigmail probably should detect that its invocation of gpg >> returns a non-zero error code and raise an error in the message >> creation step. I note tha

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10.11.14 21:52, Daniel Kahn Gillmor wrote: > When creating a signed message (whether encrypted or not), if > gpg-agent fails to sign the message, gpg 2.1.0 emits the first part > of the message, but then terminates with a non-zero error code. > >

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

When creating a signed message (whether encrypted or not), if gpg-agent fails to sign the message, gpg 2.1.0 emits the first part of the message, but then terminates with a non-zero error code. gpg 1.4.x (and i think 2.0.x, but haven't tested today) both terminate with a non-zero error code but pr