Bug#836266: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.

On 2018-10-30 19:08:32, intrigeri wrote: [...] >> Instead, I've started thinking about what a parcimonie rewrite would >> look like, one that would *not* depend on dirmngr (or, in fact, any >> specific OpenPGP implementation). If you permit, I would like to use >> this space to brainstorm such a

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.

Hi! Antoine Beaupré: > I know this is not Parcimonie's fault. It's gnupg's fault or, more > precisely, dirmngr's, but it seems difficult to change things over > there: this would require rewriting dirmngr's network routines … at least so they're network-status aware and don't treat "my system is

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.

> 4. This actually parses the packet as well and this is where things get > a little more complicated: what's an acceptable response from a > keyserver? This is another thing that's delegated to GnuPG right > now, but it would be interesting to formalize this and (self-?) >

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.

On 2017-01-10 18:28:59, Daniel Kahn Gillmor wrote: > On Tue 2017-01-10 14:15:43 -0500, Antoine Beaupre wrote: >> As things stand now, I see no choice but to stop using parcimonie, which >> means: >> >> 1. i will not update my keyring in a timely manner anymore, or; >> 2. i will reveal my keyring

Bug#836266: dirmngr: Please disable "use-tor" by default.

Package: parcimonie Version: 0.10.2-4 Followup-For: Bug #836266 I want to add my 2c to this bug report, sharing the same user frustrations as anarcat above. I don't know if any more recent tooling versions (be that parcimonie, dirmngr, gnupg, torsocks) have improved the situation, as it's not in

Bug#836266: dirmngr: Please disable "use-tor" by default.

Package: parcimonie Version: 0.10.2-4 Followup-For: Bug #836266 words -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/4

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.

On Tue 2017-01-10 14:15:43 -0500, Antoine Beaupre wrote: > As things stand now, I see no choice but to stop using parcimonie, which > means: > > 1. i will not update my keyring in a timely manner anymore, or; > 2. i will reveal my keyring social graph to the keyserver and > possible

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.

Package: parcimonie Version: 0.10.2-4 Followup-For: Bug #836266 I suffered from this same problem here on a fresh stretch install: parcimonie rewrote my dirmngr.conf to add use-tor and broke all network operations *outside* of parcimonie. This is a change of behavior and a significant regression

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: dirmngr: Please disable "use-tor" by default.

intrigeri: >> I believe the fix to use-tor issues was added in 2.1.15-9 by using adns >> for better DNS resolution. > Note that the adns support was then reverted in 2.1.16-2, "due to lack > of security support (Closes: #845078)". … and 2.1.17 upstream includes a change that might improve things

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.

Hi, Daniel Kahn Gillmor: > dirmngr has a range of problems right now with its understanding of > which hosts are alive and dead. I've been reporting them upstream, some > of them have been fixed, and some haven't yet. Cool, glad there's WIP on this front, and thanks for your work :) > avoiding

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: Bug#836266: dirmngr: Please disable "use-tor" by default.

On Tue 2016-12-06 10:34:26 -0500, intrigeri wrote: > Now, I have to admit that the currently resulting UX is sometimes > painful. In the past few months I often had to ask dirmngr to forget > that it thought my configured keyserver was down, otherwise it would > simply not even try, although my

Bug#836266: [Pkg-privacy-maintainers] Bug#836266: dirmngr: Please disable "use-tor" by default.

Dear users and fellow maintainers, I am very much in doubt about what to do with this bug report. Ideally, I think that parcimonie would start its own dirmngr instance, fork the configuration of the default instance, and enable use-tor in its own copy. I guess that's doable, but I am not

Bug#836266: dirmngr: Please disable "use-tor" by default.

Hi there, For what it's worth I've been experiencing the same issue up to now: impossible to search or get keys with "use-tor" enabled, which was forced into the config file seemingly by parcimonie. However it's just been resolved by an upgrade of gnupg/dirmngr to the latest version in sid,

Bug#836266: [pkg-gnupg-maint] Bug#836266: dirmngr: Please disable "use-tor" by default.

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 > wrote: >> Package: dirmngr >> Version: 2.1.15-2 >> Severity: important >> >> Dear

Bug#836266: dirmngr: Please disable "use-tor" by default.

On Thu, 01 Sep 2016 17:00:19 +0900 Kyuma Ohta 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"

Bug#836266: dirmngr: Please disable "use-tor" by default.

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 . So, I stopped dirmngr via gpgconf, and delete this line of