Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Package: dirmngr Version: 2.1.17-6 Followup-For: Bug #849845 Dear Maintainer, For the record - this bug shows upstream is already aware of possible problems with IPv6 - on this IPv6 host, dirmngr is unable to find the default hkps.pool.sks-keyservers.net pg2 --search-keys somekeyhere gpg:

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

at bottom :- On 08/01/2017, intrigeri wrote: > shirish शिरीष: >> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197 > >> gpg: keyserver receive failed: No keyserver available > >> Tried it multiple times but get the above failure. > > [...] > >> Any ideas what I need to

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

shirish शिरीष: > ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197 > gpg: keyserver receive failed: No keyserver available > Tried it multiple times but get the above failure. [...] > Any ideas what I need to do next ? Add a "debug-all" line in ~/.gnupg/dirmngr.conf, restart

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

at bottom :- On 08/01/2017, intrigeri wrote: > shirish शिरीष: >> in-line :- > >> On 07/01/2017, Daniel Kahn Gillmor wrote: >>> Have you restarted dirmngr since the upgrade? > >> how do I restart it ? > > systemctl --user restart dirmngr.socket > >

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

shirish शिरीष: > in-line :- > On 07/01/2017, Daniel Kahn Gillmor wrote: >> Have you restarted dirmngr since the upgrade? > how do I restart it ? systemctl --user restart dirmngr.socket :)

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

in-line :- On 07/01/2017, Daniel Kahn Gillmor wrote: > On Fri 2017-01-06 17:49:04 -0500, shirish शिरीष wrote: >> But issue is still continuing - >> >> ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197 >> >> [4:22:18] >> gpg: keyserver receive failed: No keyserver

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

On Fri 2017-01-06 17:49:04 -0500, shirish शिरीष wrote: > But issue is still continuing - > > ─[$] gpg --keyserver pgp.mit.edu --recv-keys DAD95197 > > [4:22:18] > gpg: keyserver receive failed: No keyserver available > > I tried multiple times with various other keys but didn't succeed. Have you

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Hi all, I was able to get the new version - ─[$] sudo aptitude install gnupg=2.1.17-3 dirmngr=2.1.17-3 gpgv=2.1.17-3 gnupg-agent=2.1.17-3 gpgsm=2.1.17-3 scdaemon=2.1.17-3 -y Installed it perfectly ─[$] apt-cache policy gnupg [4:19:09] gnupg: Installed: 2.1.17-3 Candidate: 2.1.17-3

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

On Fri 2017-01-06 14:47:46 -0500, shirish शिरीष wrote: > I can confirm Jaden's findings. Perhaps the content hasn't reached his > mirror yet. It's same thing at my end. I just updated to see if the > new version has come up at my end. (not even in sid/unstable) > > [$] apt-cache policy gpgv >

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

at bottom :- On 07/01/2017, Daniel Kahn Gillmor wrote: > On Fri 2017-01-06 12:49:32 -0500, Jaden Peterson wrote: >> I have no place in the topic of this bug, but I installed the patches >> you provided on January 5th onto my Debian Testing system. I would like >> to

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

On Fri 2017-01-06 12:49:32 -0500, Jaden Peterson wrote: > I have no place in the topic of this bug, but I installed the patches > you provided on January 5th onto my Debian Testing system. I would like > to notify you that gpgv2 depends on gpgv version 2.1.17-3 or greater, > which is not

Bug#849845: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

On Thu, 05 Jan 2017 16:56:40 -0500 Daniel Kahn Gillmor wrote: > Control: fowarded 849845 https://bugs.gnupg.org/gnupg/issue2902 > > On Thu 2017-01-05 08:15:06 -0500, intrigeri wrote: > > Daniel Kahn Gillmor: > >> The remaining problem for me ws that when i use tor, if i

Bug#849845: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Control: fowarded 849845 https://bugs.gnupg.org/gnupg/issue2902 On Thu 2017-01-05 08:15:06 -0500, intrigeri wrote: > Daniel Kahn Gillmor: >> The remaining problem for me ws that when i use tor, if i get back >> records, the connections fail, but the IPv6 records are not marked as >> dead, so

Bug#849845: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Hi, Daniel Kahn Gillmor: > The remaining problem for me ws that when i use tor, if i get back > records, the connections fail, but the IPv6 records are not marked as > dead, so they fail repeatedly. Same here, with a package built from commit 32bae0c609cb0c6180e9405a3d6a8fb3c0dec20e in the

Bug#849845: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

On Wed 2017-01-04 09:27:16 -0500, intrigeri wrote: > Daniel Kahn Gillmor: >> I've been able to replicate the problems described by intrigeri in >> https://bugs.debian.org/849845; i'm preparing an update to gpg with >> cherry-picked patches that resolves most of them for me. > > I'd be happy to

Bug#849845: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Daniel Kahn Gillmor: > I've been able to replicate the problems described by intrigeri in > https://bugs.debian.org/849845; i'm preparing an update to gpg with > cherry-picked patches that resolves most of them for me. I'd be happy to test these changes before you upload. If you wish, push them

Bug#849845: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Control: severity 849845 grave Hi all-- I've been able to replicate the problems described by intrigeri in https://bugs.debian.org/849845; i'm preparing an update to gpg with cherry-picked patches that resolves most of them for me. This issue is bad enough that it basically makes dirmngr

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Hi, Werner Koch: > On Mon, 2 Jan 2017 13:46, intrig...@debian.org said: >> ... which is expected if querying 127.0.0.1, that doesn't support >> SRV records. > The question is whether we should gracefully handle this failure and > return 0 records found (as done < 2.1.17)? I lack the background

Bug#849845: [pkg-gnupg-maint] Bug#849845: Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

On Mon, 2 Jan 2017 13:46, intrig...@debian.org said: > ... which is expected if querying 127.0.0.1, that doesn't support > SRV records. The question is whether we should gracefully handle this failure and return 0 records found (as done < 2.1.17)? > Jan 02 13:37:57 dirmngr[8281]: DBG: dns:

Bug#849845: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Hi Werner! Werner Koch: > The attached patch fixes this problem. Thanks for caring! I've tried rebuilding the package currently in sid with this patch applied, but it doesn't seem to be enough. The first --recv-keys triggers: Jan 02 13:36:33 dirmngr[8281]: DBG: dns:

Bug#849845: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Hi! The attached patch fixes this problem. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From b200e636ab20d2aa93d9f71f3789db5a04af0a56 Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Mon, 2 Jan 2017 10:00:33 +0100 Subject: [PATCH]

Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Package: dirmngr Version: 2.1.17-2 Severity: important Hi! since the upgrade to 2.1.17 (not sure if it's in -1 or -2), my dirmngr is unusable. Any network operation triggers: can't connect to 'hkps.pool.sks-keyservers.net': no IP address for host ... almost immediately, i.e. resolver-timeout