On Wednesday, March 18, 2015 09:21:08 PM Kristian Fiskerstrand wrote: > 11371 is expected to be for HKP, so requiring this to be TLS is bad > practice.
Oh oops. Fixed now.
> > gpg-connect-agent --verbose --dirmngr 'keyserver
> > hkps://keyserver.myriapolis.net:11371' 'ks_get 1e42b367' /bye
> >
> > gpg-connect-agent --verbose --dirmngr 'keyserver
> > hkps://holdfast.myriapolis.net:11371' 'ks_get 1e42b367' /bye
>
> What if you just update the keyserver in gpg.conf and kill the dirmngr
> (it will auto-restart)?
Done
> increase verbosity, e.g. gpg --debug-level guru --search
> b...@invaliddomain.com , alternatively specify debug / debug-level in
> dirmngr.conf along with a log-file
$ gpg --debug-level guru --search sa...@samirnassar.com
gpg: enabled debug flags: packet mpi cipher filter iobuf memory cache memstat
trust hashing extprog cardio assuan clock
gpg: DBG: [not enabled in the source] start
gpg: DBG: chan_3 <- # Home: /home/<user>/.gnupg
gpg: DBG: chan_3 <- # Config: /home/<user>/.gnupg/dirmngr.conf
gpg: DBG: chan_3 <- OK Dirmngr 2.1.2 at your service
gpg: DBG: chan_4 <- # Home: /home/<user>/.gnupg
gpg: DBG: chan_4 <- # Config: /home/<user>/.gnupg/dirmngr.conf
gpg: DBG: chan_4 <- OK Dirmngr 2.1.2 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_4 -> KEYSERVER --clear hkps://keyserver.myriapolis.net
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> KS_SEARCH -- sa...@samirnassar.com
gpg: DBG: chan_4 <- ERR 1 General error <Unspecified source>
gpg: error searching keyserver: General error
gpg: keyserver search failed: General error
gpg: DBG: chan_4 -> BYE
gpg: DBG: [not enabled in the source] stop
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: secmem usage: 0/32768 bytes in 0 blocks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
