could be a problem between Enigmail and GPG2.1 .....

i think gpg2.1 has only recently become available

what i would try: set Enigmail to use gpg rather than gpg2.   go back and generate a key using gpg then rather than gpg2.1    this clearly isn't where you want to end up but the test results could very likely be useful

you are not playing with EC Curves  ---- are you?


On 02/21/2017 01:37 PM, enigmail-users-requ...@enigmail.net wrote:
This is because the keys were generated with GnuPG 2.1. GnuPG 2.1 stores
the keys differently than GnuPG 1.4 and 2.0; therefore you don't see
these keys with "gpg".

As you do have a list of keys from gpg2, I'd recommend you set the path
for GnuPG in Enigmail to /usr/bin/gpg2 (menu Enigmail > Preferences),
such that these keys are visible in Enigmail.

-Patrick

-- 
/Mike
_______________________________________________
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

Reply via email to