Hi, intrigeri <intrig...@debian.org> (2018-06-30): > Thanks for the prompt reply!
No worries. > OK, so it looks I was wrong to reassign to parcimonie. > Before I draw conclusions, I need a little bit more info: > > - Can you please check that tor listens on 127.0.0.1:9050 (TCP)? Yes: tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN - > - Does "torsocks curl https://www.debian.org/"; work fine? Yes, I get the index page in less than a second. > - Could you please share your ~/.gnupg/dirmngr.conf and > ~/.gnupg/gpg.conf with me (possibly privately)? I don't think there are (or were) private things in there. I did rename .gnupg/ away a while ago, trying to get back to a default configuration (which I never tweaked much anyway) before reporting this issue. AFAICT the only bits of tweaking I did was reinjecting my private keys in there. I suppose what you're seeing below is indeed the result of parcimonie's integration bits (App/Parcimonie/GnuPG/Interface.pm at first glance), with the auto enabling of use-tor. kibi@armor:~$ cat .gnupg/dirmngr.conf ###+++--- GPGConf ---+++### #use-tor use-tor ###+++--- GPGConf ---+++### Sat 30 Jun 2018 16:33:06 CEST # GPGConf edited this configuration file. # It will disable options before this marked block, but it will # never change anything below these lines. No gpg.conf at all. Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
