Discussion:
Processed: Re: [pkg-gnupg-maint] Bug#849845: dirmngr: Can't resolve keyserver hostname anymore
(too old to reply)
Debian Bug Tracking System
2017-01-04 14:10:01 UTC
Permalink
Raw Message
severity 849845 grave
Bug #849845 [dirmngr] dirmngr: Can't resolve keyserver hostname anymore
Severity set to 'grave' from 'important'
--
849845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849845
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
intrigeri
2017-01-04 14:40:01 UTC
Permalink
Raw Message
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 to the packaging Vcs-Git (in a dedicated branch if you
prefer) and I'll build & try it :)
Daniel Kahn Gillmor
2017-01-04 18:30:02 UTC
Permalink
Raw Message
Post by intrigeri
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 to the packaging Vcs-Git (in a dedicated branch if you
prefer) and I'll build & try it :)
Thanks, intrigeri! I've pushed 32bae0c609cb0c6180e9405a3d6a8fb3c0dec20e
to Vcs-Git master branch. Please let me know how it goes for you.

--dkg
Daniel Kahn Gillmor
2017-01-06 12:30:02 UTC
Permalink
Raw Message
Control: fowarded 849845 https://bugs.gnupg.org/gnupg/issue2902
The remaining problem for me ws that when i use tor, if i get back AAAA
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 Vcs-Git (which by the
way fixes the other problem I've reported here :)
thanks for the reportback! I've reported the remaining issue upstream
(see the url above). I'll do an upload to unstable with the
intermediate fix later today, unless i can sort out a fix for the whole
issue first.

--dkg
Debian Bug Tracking System
2017-01-23 19:10:01 UTC
Permalink
Raw Message
reassign 849845 tor
Bug #849845 [dirmngr] dirmngr: Can't resolve keyserver hostname anymore
Bug #850606 [dirmngr] dirmngr: can't resolve ipv6 addresses when use-tor is enabled
Bug reassigned from package 'dirmngr' to 'tor'.
Bug reassigned from package 'dirmngr' to 'tor'.
No longer marked as found in versions gnupg2/2.1.17-3 and gnupg2/2.1.17-2.
No longer marked as found in versions gnupg2/2.1.17-3 and gnupg2/2.1.17-2.
Ignoring request to alter fixed versions of bug #849845 to the same values previously set
Ignoring request to alter fixed versions of bug #850606 to the same values previously set
forcemerge 851798 849845
Bug #851798 [tor] tor: IPv6 connections through tor do not appear to work
Bug #849845 [tor] dirmngr: Can't resolve keyserver hostname anymore
Changed Bug forwarded-to-address to 'https://bugs.torproject.org/21269' from 'https://bugs.gnupg.org/gnupg/issue2902'.
Changed Bug forwarded-to-address to 'https://bugs.torproject.org/21269' from 'https://bugs.gnupg.org/gnupg/issue2902'.
Severity set to 'normal' from 'grave'
Severity set to 'normal' from 'grave'
Failed to forcibly merge 851798: It is nonsensical for a bug to block itself (or a merged partner): 850606.
--
849845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849845
850606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850606
851798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851798
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...