l...@gnu.org (Ludovic Courtès) writes: > Ni* <niaster...@grrlz.net> skribis: > >> I got it to the point where it works again, meaning searching for >> keys (although I am unsure wether it uses hkp or hkps protocol), etc. > > [...] > >> What I did was start from scratch with GnuPG 2.1: >> >> cat gpg.conf >> keyserver-options no-honor-keyserver-url include-revoked >> fixed-list-mode >> keyid-format 0xlong >> personal-digest-preferences SHA512 SHA384 SHA256 SHA224 >> default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 >> BZIP2 ZLIB ZIP Uncompressed >> use-agent >> verify-options show-uid-validity >> list-options show-uid-validity >> cert-digest-algo SHA512 >> no-comments >> with-fingerprint >> no-emit-version >> >> cat dirmngr.conf >> keyserver hkp://hkps.pool.sks-keyservers.net >> hkp-cacert /home/myusername/certificates/sks-keyservers.netCA.pem > > Do you know which of these options made the difference? > > Thanks, > Ludo’.
I had initialy issues with a pinentry, which were solved with adding the "default-cache-ttl" to gpg-agent.conf ~/.gnupg$ cat gpg-agent.conf pinentry-program /home/pathto/.guix-profile/bin/pinentry-curses default-cache-ttl 86400 cat ~/.gnupg/gpg.conf use-agent -- Ni* -- http://www.libertad.pw Email is public. Talk to me in private: https://psyced.org:34443/~niasterisk privacy respecting, secure communication: BM-2cSj8qEigE3CMaLU3CwPZf7T3LvzvnttsC (bitmessage)
