On 27/08/15 14:58, intrigeri wrote: > Hi Ximin, > > Ximin Luo wrote (23 Aug 2015 19:10:35 GMT) : >> But I have a different solution to this that bypasses the perl, simply by >> having >> parcimonie-torified-gpg itself read $GNUPGBIN - patch supplied. I chose >> GNUPGBIN >> because that's what caff also uses. > > Cool! I'm glad you've found a solution that works for you :) > > But, wait: does the resulting wrapper really torify communication with > the keyservers? On my system, with gnupg2 2.1.7-2, it doesn't. This is > not surprising: in GnuPG 2.1+, dirmngr handles all such communication, > so wrapping the call to gpg with torsocks is not supposed to impact > dirmngr. What do you think? >
Hmm, looks like you are right. `torsocks gpg2` only affects dirmngr, if it spawns a new dirmngr. Otherwise, it will use the existing process, which may not already be torified. gpg2 does not appear to have an option to use a separate dirmngr for a single run. We'd have to force the user's default dirmngr to be torified, and it's not yet clear to me the best way to do that. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
