OS X - can't open GnuPG-2.2.5.dmg

Hi, just tried to update my GnuPG install on my iMac, from the SourceForge repository, but the image won't open. The shasum matches and with DiskUtility it shows also that the .dmg is o.k. Downloaded several times, with the same result. :-( Regards Stefan   0xD68B6EAC6ECF3AB6.asc

Re: GPG is not working because of gpg.conf

On Tue, 6 Mar 2018 10:30, tliko...@iki.fi said: > The feature is not documented in 2.1.18. Is it documented in newer > versions? It is kind of an emergency option in case we accidently remove an option ;-) Shalom-Salam, Werner -- # Please read: Daniel Ellsberg - The Doomsday Machine

Re: GPG is not working because of gpg.conf

Werner Koch [2018-03-05 13:24:28+01] wrote: > gpg searches for its configurarion file in this order (I use 1.4.23 as > example): > > gpg.conf-1.4.23 > gpg.conf-1.4 > gpg.conf-1 > gpg.conf That feature is not documented in 2.1.18 but it seems to work. (I tried "gpg.conf-2.1".) -- ///

Re: [gpgme] generate a wheel of the python bindings

All problems disappeared with latest source. So everything is ok :) Thank you once again 2018-03-06 3:15 GMT+09:00 Matt : > Thanks for the detail answer. > >> With GPGME as a dependency ... Claws or Mutt/Neomutt? > Nope, just "alot" :) https://github.com/pazz/alot > > Your

Re: GPG is not working because of gpg.conf

On Mon, 5 Mar 2018 19:30, b...@adversary.org said: > Good to know, but will a version of GPG always select the highest in a > listor the closest number to its own version number if there's not an > exact match? No, the algorithm views the version as a string simply trims the dot/dash delimted

gpg agent Could not add identity agent refused operation

Hello, I'm trying to use gpg-agent to manage my ssh key though am getting this error: ~ ᐅ ssh-add ~/.ssh/id_rsa Enter passphrase for /home/admin/.ssh/id_rsa: Could not add identity "/home/admin/.ssh/id_rsa": agent refused operation Is this because I have a 16k RSA ssh key? How can I debug

Re: GPG is not working because of gpg.conf

Werner Koch [2018-03-06 09:53:01+01] wrote: > Note that there is another compatibility feature which can be used to > ignore errors due to new options. For example: > > ignore-invalid-option foo bar > verbose > foo > This feature is available since 1.4.13 and 2.0.20 . The feature is not