Bug#780628: parcimonie: support gpg2

2016-03-29 Thread intrigeri
Hi, Daniel Kahn Gillmor wrote (25 Sep 2015 04:40:22 GMT) : > the usual way to deal with this is just to update the dirmngr config > file to have the parameters you want. > You can even do that programmatically with gpgconf, for example: > [...] > see gpgconf(1) for more details. you may also be

Bug#780628: [Pkg-privacy-maintainers] Bug#780628: parcimonie: support gpg2

2015-10-04 Thread Jérémy Bobbio
clone 780628 -1 reassign -1 gnupg2 retitle -1 gnupg2: please add support for reaching out to keyservers through Tor tags -1 + upstream block 780628 by -1 thanks Daniel Kahn Gillmor: > > That said, it seems Werner is thinking about this problem upstream, by > > adding --use-tor and --force-tor

Bug#780628: [Pkg-privacy-maintainers] Bug#780628: parcimonie: support gpg2

2015-09-25 Thread Daniel Kahn Gillmor
On Wed 2015-09-23 15:10:10 -0400, nodens wrote: > If it's created on-demand by existing gpg process, we could kill it > after launching our gpg process and refresh keys to launch a new one > (but the race condition issue may still occur if any gpg2 process can > launch a dirmngr). the usual way

Bug#780628: parcimonie: support gpg2

2015-09-23 Thread nodens
Hi, some thoughts on this issue, maybe it can stir new ideas. We can control (kill) the dirmngr using gpgconf --kill dirmngr. We can't kill it just before launching our torified gpg process, however, because there is a risk of race condition (another one could be launched before we actually run

Bug#780628: parcimonie: support gpg2

2015-08-27 Thread intrigeri
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

Bug#780628: parcimonie: support gpg2

2015-08-27 Thread Ximin Luo
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

Bug#780628: parcimonie: support gpg2

2015-08-27 Thread intrigeri
Ximin Luo wrote (27 Aug 2015 13:28:37 GMT) : We'd have to force the user's default dirmngr to be torified, Yep, that's what I had in mind. and it's not yet clear to me the best way to do that. Same here. I didn't put much thought in it yet. Cheers, -- intrigeri

Bug#780628: parcimonie: support gpg2

2015-08-23 Thread Ximin Luo
On 17/03/15 01:14, intrigeri wrote: One workaround in the meantime is to edit /usr/bin/parcimonie-torsocks-gpg, but of course this changes things for the entire system. I also tried putting an override in ~/bin/ and adding this to PATH, but it didn't work. I find this surprising, given I

Bug#780628: parcimonie: support gpg2

2015-03-16 Thread Ximin Luo
Package: parcimonie Version: 0.8.4-1 Severity: wishlist Hi, gpg2 is getting more usage. Please allow parcimonie to work with it, e.g. by a CLI or ENV setting. One workaround in the meantime is to edit /usr/bin/parcimonie-torsocks-gpg, but of course this changes things for the entire system. I

Bug#780628: parcimonie: support gpg2

2015-03-16 Thread intrigeri
Control: tag -1 + upstream Hi Ximin! Hi, gpg2 is getting more usage. Please allow parcimonie to work with it, e.g. by a CLI or ENV setting. Yes! I've got bad news: I probably won't have time to do that myself soon. I've got good news: * I'm using parcimonie vith gpg2 myself (I've got a