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 buffering going on and that may be the reason for the different behavior. Given that gpg is designed to work in a pipeline, it does not store any data and thus a cancel or any other error may leave unfinished output. If we know that we are writing to a file created by us, that file is removed on error - but for obvious reasons not if it goes to stdout. What we can do is to start implement a pre-sign command in gpg-agent which unprotects the key and then waits for the actual sign command at the end of the input data (which may take some minutes for large file). GPGME's UI-server protocols defines something similar. * 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 that it appears to do so properly for when generating non-encrypted PGP/MIME-signed messages, it's just failing at PGP/MIME encrypted+signed messages. Maybe because of that ugly micalg MIME parameter which inhibits one-pass processing? We should anyway ignore that parameter - it is useless for OpenPGP. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
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 gnupg 2.1, as mentioned). No unsent mail, same error alerts as already posted. Ludwig -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJUYoHoAAoJEA52XAUJWdLjL/wIAKigmlvrwNOIxxvJ+AZ85fhA clBMJIFz3+DJSg1UMCLPzYG8UAOfyDGVsCq5GapjtbsBPw/QEmv2t433eEK25fqb f/ic6XJgRrXzLlaL82FMCWh6iE2XNg4zTW+YCWrBmuSekb/K8SNwAytMnIT8Cdfj HQ0HlifRJ+Ax7UQ4zyLMBFmhXn8wozvUVX2AYH+EZIzTF6siBAgZysIlbIjD5tas EpWPpGcJC6STuglV6MqXEud+ZqfnEe7Av5ZoY4SRlnuxzwfUqqEJtaiEKLh11Fu7 McPxui871cmSns7/yfBEIpdhownOocMlzUMsaCgKUTF5gyR/bwcKI68g/rWw3cM= =jwDe -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
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 sure you're doing encrypted+signed? are you also doing PGP/MIME? Yep. Maybe there's a version/platform difference here? what are you using? This is on Mac OS 10.10, TB31.2 and the latest enigmail nightly. I didn't use 1.7.2 What version of GnuPG are you using? 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). --dkg signature.asc Description: OpenPGP digital signature ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
