-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 21.05.15 19:56, Philip Jackson wrote: > On 18/05/15 14:06, Philip Jackson wrote: >> On 18/05/15 08:32, Patrick Brunschwig wrote: >>>> And how could enigmail display an alertbox which contained >>>> no >>>>> message ? >>> I think because of this (which is issued at the end of the >>> decrypt/verify command): gpg: Ohhhh jeeee: can't encode a 512 >>> bit MD into a 608 bits frame >> >> Well thank-you for the efforts, Patrick. >> >> That particular key is still not visible anywhere within >> enigmail's key management on this machine although clearly >> enigmail is using it. I just retried opening Thunderbird and >> reading only this single message and asking enigmail to show me >> the key info. >> >> The log file shows the 'Ohhhh jeeee' message 3 times but I never >> had the blank alertbox again (only the very first time). >> >> I'll have to leave this as one of those unsolved mysteries of >> life. > > Just a note to close the loop on this matter. > > A couple of days after my last posting, I wanted to look at a key > listing so used "gpg2 -k". The listing was not complete and ended > in the same odd "Ohhhhh jeeeee..." message. However I was able to > get the full listing using "gpg -k" > > So I took this issue up on the gnupg-users list and Werner came up > with this - > >> gpg tried to verify a key signature and ran into that problem. >> Of course it should not abort here. It would be helpful if you >> can you figure out which key causes the problem. Maybe the key >> shown last or the one which would be shown next. Running with >> "--debug 64" might give some hints. > > I found a key causing this problem. "gpg2 --delete-keys <keyID>" > failed on the problem key giving the same 'Ohhhh jeeee...' message > but gpg did the job. > > Once the problem key had been deleted, enigmail then displayed > correctly the key that it previously wouldn't display - either in > Key Management or in 'Details/View key properties'. > > I don't understand what was the connection between the key I > deleted and the one that enigmail wouldn't display - the one was > not used as a signatory on the other. Nor were they adjacent on the > keyring.
It may depend on the sequence in which the keys are listed in gpg2 - --list-keys (without any specific key ID). If the key causing the problem was listed before the missing key, then gpg might have stopped at that point and not listed any subsequent keys. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVXsu6AAoJENsRh7ndX2k7i84P/3PPYm5n9bS9L1Knq9PwuNgV ckK9jw/lQ8xeCezQqN7J6IEsH05EAIGQV3KX+RVli1JuUyjnaqsU6poV1JeYIcAV RKJWHOQvwgfkNpHzrqDi4UDV5+eOYQvmLwi0qADtleandxIvKEgffCjMQeeWZqO1 HldpSOblLCAbfoKWihY3NLY8Gupv8jqAT1t+cphCW9rxmX35MZnjFQN9GcXAxZGu /KwMstQZDe6faKm/H2kSCQvR7n2D+D9S7d5IAZtCnScgV++BoGHsvYxDKjn9pF/t cGKG52nc0yqCcgoDV3vTOnTWzFppo7XmVOcQt7JnYnpA2o/2TQpWO2U+1oYwllAI EMsAVT95oaPex/UGkLzuSXNVZUZLAzVvof/8muQxMQOT3iDS9H/c9rOuB9g+yuEe 34rs8/vK4vIsz6YXd+EVdYU+MHhLhnui8ZcCDZx6+xU7DFSTt/BTiO/vzK6mnOpU Zig3jvTk04CjFN6wJvU1YKcyvAw/0xqJx9HE7Cy8GuFmTs2TzatVG/KdSWGk2hMr ticM5/wtUW+ZhnSfDb1KEE+dJWvLbVjHGX6PSbIx6bULI36XzsHvauIwIjZjKmU2 VEQthNXddyDIsE5ze8olvAe1HEbOcFgReR9O+nC+TL3be8ojcROQyJwerjoqD/zE gNXwY2gdA2teoyQHdcDn =feJk -----END PGP SIGNATURE----- _______________________________________________ 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
