Control: reassign 836266 parcimonie Control: affects 836266 + dirmngr On Wed 2016-09-07 17:31:17 +0200, Felipe Sateler wrote: > On Thu, 01 Sep 2016 17:00:19 +0900 Kyuma Ohta <whatisthis.sow...@gmail.com> > wrote: >> Package: dirmngr >> Version: 2.1.15-2 >> Severity: important >> >> Dear Maintainer, >> Running gnupg2 with dirmngr, sometimes failed to connect to keyserver. >> I checked configuration files, automatically add "use-tor" to >> ~/.gnupg/dirmngr.conf .
dirmngr defaults to having use-tor set to false, and does not automatically add use-tor to ~/.gnupg/dirmngr.conf >> So, I stopped dirmngr via gpgconf, and delete this line of dirmngr.conf, >> and running gnupg2 to access to keyserver, this succeeded. >> >> But, after about 15min, re-run gnupg2 to access to keyserver, faied. >> I checked dirmngr.conf again, added "use-tor" again I suspect that you have parcimonie installed, since it appears to automatically ask dirmngr to use tor: https://codesearch.debian.net/search?q=use-tor&perpkg=1 Do you have it installed? Is it configured and running for you? >> At some ISPs, tor connection has rejected by default, maybe gnupg2 >> fails to connect to keyserver by default. > > Not only this, but dirmngr does not detect the availability of tor, > and thus fails to work if tor is not installed (or uninstalled after > the first use). If dirmngr is configured to use tor, and tor is off or broken or uninstalled, it should indeed fail to work (rather than contacting the keyservers without using tor). that's proper behavior, i think. (though i agree that better error messages or warnings would make the failure easier to diagnose and understand, and would be a positive improvement) I'm reassigning this bug to parcimonie, because that's where use-tor is being set automatically. --dkg
signature.asc
Description: PGP signature
