Re: [Enigmail] enigmail-users Digest, Vol 32, Issue 24
On 15-03-20 06:01 PM, wrote: >Did you try to override the gpg that enigmail finds ? > >In enigmail/preferences/Basic you can check the box "Override with " >and enter >the path to gpg2 in the field alongside. > >If you don't know where gpg2 is hiding itself, try "which gpg2" in a >terminal. >You should then get the path to gpg2 > >Philip This proved to work quite well, thank you. ___ 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] SHA Info missing
> I don't see any SHA info on my messages, whether they are just > signed, sent with Inline PGP, or with PGP/MIME. Is there a setting > or configuration I should know about? (using 1.8) This information is not displayed by Enigmail. All of the hash algorithms used in modern OpenPGP are safe and may be used with confidence, so reporting detailed algorithm information is "cognitive spam" that tends to confuse people more than it sheds light on anything important. If you want to get detailed information on a message, try saving it to disk and feeding it through gpg -. :) 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
[Enigmail] SHA Info missing
I don't see any SHA info on my messages, whether they are just signed, sent with Inline PGP, or with PGP/MIME. Is there a setting or configuration I should know about? (using 1.8) -- RLB ___ 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] New GnuPG 2.0.27
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi David, > Googling this suggests it may be a conflict between gnome-agent and the > gpa-agent. I am running Ubuntu 14.10. sorry, but this IS off-topic (for this list) now ;-) But there is some hint on https://www.enigmail.net/support/gnupg2_issues.php on how to disable gnome-keyring - don't know if that's your issue, I'm on W8 ... Olav - -- The Enigmail Project - OpenPGP Email Security For Mozilla Applications -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/ iQGcBAEBCAAGBQJVDKUuAAoJEKGX32tq4e9WkBUL/3tUAxc85+dtRrYDGoBEhQcX jmHFox6hoOpEWeTLPvIrB4Rr+5NzSoX+TZ3OdrFpZ1H+CgWlzKlKreCeN/KZVKuP 2oLcVSJm3tn7dXSPJpOfBB01rOcT7mIDn1IBgC7fr/Q/jw3mEbf89BZ1V9VD/IDH Kf9V7kROkfKR3xwQg9xP+FbbUw5wY2yamLqI86612NZYwnXYStdMjq/It0XiAgk6 OlS4trCAyBau7Mh5EIn1+/j9TeCCy8dqDind0AjNG1IHnP6yLtd4no4hWpZDgJaP LwkS0T7p+isef9SL/MLPF5hmkHoLYxuNDN5AB5wcGRpEdLQECMq7Lf45fM3XBTZQ HHIYpBeymmA00KzXasZa8FDTnzJOCzF1YlFK5T1YdX5pzgaF6wxTrnedXtmr5QHp xAqtsncUk96R8LCmTzz0+ZU6A9IAb+HgHcvCV3GbhL5b0UElldXCuprpmjiJioiB O+EROASB0nP3HaE3FZtSJLYmrRmIMEr30YinTurtjg== =XCbe -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] New GnuPG 2.0.27
On 03/20/2015 06:01 PM, Olav Seyfarth wrote: > >>> installed GnupG 2.0.27, via Gpg4Win 2.2.4 > >> reason is, that GnuPG 2.0.27 errors out if it detects keys using MD5. > >> Workaround: use allow-weak-digest-algos in Enigmail or gpg.conf > > Is there a method to search for such keys? > > I definitely *don't know whether this is correct*, but what I did is > > gpg --list-key 0x > This, in my case, *seemes* to list all affected keys. Don't ask me why. > I stumbled upon it while I got displayed keys with FPR all zero... > > I exported these keys to be able to roll back ... > > gpg --export 0x > md5_keys.gpg > > ... and deleted them manually by executing this as long as it still > found some: > > gpg --delete-keys 0x > > After that cleanup, I had no more errors even without > allow-weak-digest-algos . > > Olav > -- > The Enigmail Project - OpenPGP Email Security For Mozilla Applications > > ___ > 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 > > I got no keys but probably because I had done a manual scan in Kleopatra which will show the hash if you hover over a key. However, I am still getting a gpa error. Here it is: The GPGME library returned an unexpected error at keytable.c:150. The error was: Unsupported certificate This is either an installation problem or a bug in GPA. GPA will now try to recover from this error. Googling this suggests it may be a conflict between gnome-agent and the gpa-agent. I am running Ubuntu 14.10. 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
Re: [Enigmail] New GnuPG 2.0.27
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >>> installed GnupG 2.0.27, via Gpg4Win 2.2.4 >> reason is, that GnuPG 2.0.27 errors out if it detects keys using MD5. >> Workaround: use allow-weak-digest-algos in Enigmail or gpg.conf > Is there a method to search for such keys? I definitely *don't know whether this is correct*, but what I did is > gpg --list-key 0x This, in my case, *seemes* to list all affected keys. Don't ask me why. I stumbled upon it while I got displayed keys with FPR all zero... I exported these keys to be able to roll back ... > gpg --export 0x > md5_keys.gpg ... and deleted them manually by executing this as long as it still found some: > gpg --delete-keys 0x After that cleanup, I had no more errors even without allow-weak-digest-algos . Olav - -- The Enigmail Project - OpenPGP Email Security For Mozilla Applications -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/ iQGcBAEBCAAGBQJVDJiiAAoJEKGX32tq4e9Wb1wL/23MvGne7muHlOhRksem2h97 5qYEV8XHuSOLBF1yqYqlstDNhi332ekmuwl2PP0oZQaFO8FdlEEwlG+wLcZ9+8Kh 5n6j/W/4NVjpcw1u+2Sy/VRSvklUYCyM1Ye6moZycEY9yD6je5OVkWeDnj7oAcrF oAQkPFLI+H1xiod3vbwPUmJ4lD8Ho8Cl1KYytVAfnfiX9iHrlqYVCyArnsa+bgDE YtuAhtQkXJwxoxfKBrQWgHlTzsJmEfjkR7y4qCGZN/djQsUUN7Esvxrtd8x28TnO N0GAKRrEwDRej5OvMH3n2qK/bTbnyc//NvSdulmv/zKXDMFWMNh5A8S4bZyOfvMs 6LpMWpR5foPX47Z4rTKqsXYoX7OhaFs5hLKwzLzZ+xEGg8VfWK9WHHrUQ0TXxvF+ NkW0zfvU7CORkJl/JT/WlPLZQXs8Y9OnxilFyPnoLalKYSiXezbHCdhR/K7M3tC6 ldtBOIs9rkYTvCWykrW2brD/1o8gEuit51xDLCBi6A== =BSKV -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] New GnuPG 2.0.27
On 03/18/2015 12:04 PM, Bob Henson wrote: > On 18/03/2015 12:57 pm, Ludwig Hügelschäfer wrote: >> On 18.03.15 12:11, Bob Henson wrote: >>> I just installed the new GnupG 2.0.27, via Gpg4Win 2.2.4 vanilla. >>> I couldnot access the Enigmail key management window at all - >>> getting the following error message:- >>> error The spinner was indicating that it was trying to load the >>> keys, but nothing happenedafter a considerable wait. >>> I reinstalled it over itself to no avail. I re-installed 2.0.26 >>> via Gpg4Win 2.2.3 and all was immediately restored to full >>> functioning . Not being very technical, I have no idea why this >>> should be but thought it would be of interest, and that someone >>> might know why? I'm not currently connected to the GPG4Win forum, >>> so I can't say if it has been mentioned in there. >> The deeper reason is, that GnuPG 2.0.27 errors out if it detects weak >> digest algorithms. They are used on older keys, having the MD5 hash. >> See the release notes for 2.0.27: >> http://lists.gnupg.org/pipermail/gnupg-announce/2015q1/000362.html >> This behaviour prohibits loading the key list, as Enigmail respects >> the exit code of GnuPG and thinks, there is a serious error and no >> usable output. So, this is no bug which was introduced with Enigmail >> 1.8, you would certainly get the same behaviour with 1.7.2. >> >> As a first aid, this can be fixed by the following procedure: Open >> Enigmail -> Preferences. Ensure the "Advanced" tab is shown. If not, >> click on "Show Expert Settings and Menues". Select the "Advanced" tab. >> Put the following in the field "Additional parameters for GnuPG": >> >> --allow-weak-digest-algos >> > OK, I'll use that for the moment whilst I work out which of the keyring > have the old hash. Thanks for the help. > Is there a method to search my keyring for keys with the MD5 hash other than looking one by one? ___ 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
[Enigmail] gmane + signing (was: New 1.8 toolbar on the composition window)
On 2015-03-18 03:23, Doug Barton wrote: > I am conducting an experiment in the efficacy of PGP/MIME signatures. > This message should be signed. If it is not, or the signature does > not validate, please let me know how you received this message > (direct, or to a list) and the mail software you use. Thanks! Huh. I see a signature.asc attached, but no other indication that your message is signed. Using TB 31.4.0 with Enigmail 1.7.2 (both as provided by Fedora 20). Note that I am interacting with the list via [news://news.gmane.org/gmane.comp.mozilla.enigmail.general]. I get warnings (due to missing public keys) for inline signing. Seems like I should see the same for your message if Enigmail was recognizing that there is an attached signature... -- Matthew ___ 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
[Enigmail] (Bug) Enigmail notices illegible in some color schemes
The signature verification/warning banner at the top of messages is illegible when using a light-on-dark color scheme; see attached. Hard-coding the foreground color as well as the background color would be an improvement, but please note that some users have trouble reading dark text on a light background. It would be best if the colors are configurable, or at least adapt to the user's color scheme. -- Matthew ___ 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] GPG1 issue
On 20/03/15 15:27, Leon Smith wrote: > Hello, > > On my computer I have both GnuPG1 & GnuPG2 installed, however for some > odd reason Enigmail refuses to detect GnuPG2 and only detects GnuPG1. > What exactly ought I to do to fix this? > Did you try to override the gpg that enigmail finds ? In enigmail/preferences/Basic you can check the box "Override with " and enter the path to gpg2 in the field alongside. If you don't know where gpg2 is hiding itself, try "which gpg2" in a terminal. You should then get the path to gpg2 Philip 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
Re: [Enigmail] GPG1 issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 20.03.15 15:27, Leon Smith wrote: > Hello, > > On my computer I have both GnuPG1 & GnuPG2 installed, however for > some odd reason Enigmail refuses to detect GnuPG2 and only detects > GnuPG1. What exactly ought I to do to fix this? The sequence of searching for GnuPG is this: 1. in all directories of PATH environment variable 2. c:\gnupg;c:\gnupg\bin;d:\gnupg;d:\gnupg\bin (Windows only) 3. Windows registry 4. /usr/bin;/usr/local/bin (not Windows) Each directory is checked for gpg2, then for gpg, then for gpg1. The first found executable will be used. - -Patrick -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVDDmYAAoJENsRh7ndX2k7/DUQAJCrpktr8r8wpTw0f399k4ns KU94ALUGkzVP3L6heQH8I86/wIFZ4iuig/Q/YKiEn/4ylsO3wV2/ZGbPhRiEuLW6 C/Hgwem2XGTYoCTf7WUXBdVonptRdbsBs82ORE1IoqE/u0P0YTW0xYjhnuJrzYJ7 d5o4WshjcBgNyzBredRdzHl5gTmk2yXsCuqXrolPyca/9AkdQToRtE/kJGvjils7 SnDFxZhz7zE/IrTXWSftVC8HjUZsn2ilGucuH0VGK4UeubynMYQ3GxhES/AUTd1y sQfuZW3izcMpg5lWtrKV8SyU7kJCGmd5XuN+P6/O9KyyX87ZfsSQ8yIy/Zhs5OnH OfXfvw76rnob4nrk4DmC+HMOkUY4dMcWxWTSKt9GVVbL/sbDfxVum6KIgM+mITe5 i+2evu3YlXx5cYzgRPoIlfmZAbWnHiRzCXuOrMJGxiKoLoLbERwz3UHdPXWjR4PJ 5LlfsA9Z+q+MNsXzIT9bMa5gOiZ+emTP9Ta1xLtsuQyzlVzIaS20fGh8GUERXnCN IIQLK9AQ0ZjUMJ5qTo8VqXat4G7qHyZHt95czv1NHkoLiP6DmJkeAo8KwdUDoBns aDSmq4yY8BNm2wji0CuFqeBRMuEpKyMuFe9A5EXc8dS8yEn8+bg8CFYASZlbxjKG RVQDaOqZtdY2TVLDWHgh =YU+C -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
[Enigmail] GPG1 issue
Hello, On my computer I have both GnuPG1 & GnuPG2 installed, however for some odd reason Enigmail refuses to detect GnuPG2 and only detects GnuPG1. What exactly ought I to do to fix this? L.S. ___ 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] Dropped Support for GnuPG 1.4.x in Nightly Builds
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 20.03.15 00:31, Daniel Kahn Gillmor wrote: > On Thu 2015-03-19 13:36:17 -0400, Patrick Brunschwig wrote: > >> I pushed a number of changes that remove support for GnuPG 1.x >> from Enigmail. The main objective was to remove anything >> concerning passphrase handling from Enigmail, as GnuPG 2.x does >> this by itself. > > gpg 1.4.x can also do the passphrase handling by itself, as long > as --use-agent is passed to it in each invocation (and the agent > is running). > > Do we want to explicitly drop 1.4.x anyway, or just say "we don't > support 1.4.x without using the agent"? Support for 1.4.x is dropped now entirely. There are also other differences e.g. in the output of GnuPG 1.4.x when accessing keyservers that I don't want to support anymore. - -Patrick -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVC8t2AAoJENsRh7ndX2k7JEIQALNQvXG0F9Z/Gx5aLe3s3Vap OW3KNOjJWmp2+yCRRsO+opod6R0vDRBvgWTcI1lyaAM5EOdZomoA+djOS/xRtPRJ Jm6pSxzhxwY7Ci16XNwuMjejn9mATG5MB0vHMwWazTqj+NGrn+ULoo5tLnxoC0yX T8gkKzYwxyGLRMA89cQs29SED31eOgjpYNDr1NmGB4hLAvG6YKea9KFjagVEKJu+ 4F2FaEiIJ0VxyEXaBzH2GuuCZIv9UJbb7Q6KnnoZsdtH8gdrEB9yC7J8vMvv8AKD d2+cg1cSeaeAkJlbTNl+sjT1Hlk8o8ntWdlamn1frJomsOuDH0NuOPYDGacsjNmp jGxAeOfqdeZ/WDW2bKKKcBvP2eQ87lu4Fqe8Rtu8MJSE+MVptJOhz/MRo3VWcpqn Zyb2rr35dm8FHHflR9ZwsseaVMs0kxzgvrqgl1ENVlJ6N69AFWCk6pryO61AmCwd YRx7ZT3CgbKl0psZ76oAk2HlSvzNhciQfkHnLbch6Bm1BBVEgsTaKRCHJkEy7CIV Quf0Dbj23tsueL1JhPqJBw4S8ygkDNF9JYZXN+8JTK5Qm6Vn1/s43ZjW8h1WVnm0 KMgNZXNqTM5DL6Pf7VaoCv3rpQbChX97oEQDGcv9/QJR74g0eMLb6BFf85dhFeHy VFJeWh+NeKDkFkknIopa =veoA -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
