Your message dated Sat, 5 Apr 2025 13:20:36 +0200 with message-id <[email protected]> and subject line Re: Bug#860352: [pkg-gnupg-maint] Bug#860352: Bug#860352: gnupg: cannot handle hkps keyservers has caused the Debian Bug report #860352, regarding gnupg: cannot handle hkps keyservers to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 860352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860352 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnupg Version: 2.1.18-6 Severity: important Hi, this is a very similar case to #811146 which supposedly is resolved, but it isn't: Relevant ~/.gnupg/gpg.conf lines: keyserver hkps://hkps.pool.sks-keyservers.net keyserver-options no-honor-keyserver-url Relevant ~/.gnupg/dirmngr.conf lines: hkp-cacert /usr/share/gnupg/sks-keyservers.netCA.pem $ gpg --version gpg (GnuPG) 2.1.18 ... $ dpkg -l gnupg ... ii gnupg 2.1.18-6 amd64 GNU privacy guard - a free PGP replacement Searching with dirmngr directly succeeds (see above bug report), but gnupg fails with General error $ gpg -vvv --debug-level 10 --search-key 58E11BB1E414D9AD gpg: using character set 'utf-8' gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat trust ipc clock lookup extprog gpg: DBG: [not enabled in the source] start gpg: DBG: chan_3 <- # Home: /home/norbert/.gnupg gpg: DBG: chan_3 <- # Config: /home/norbert/.gnupg/dirmngr.conf gpg: DBG: chan_3 <- OK Dirmngr 2.1.18 at your service gpg: DBG: connection to the dirmngr established gpg: DBG: chan_3 -> GETINFO version gpg: DBG: chan_3 <- D 2.1.18 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KEYSERVER --clear hkps://hkps.pool.sks-keyservers.net gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_SEARCH -- 58E11BB1E414D9AD gpg: DBG: chan_3 <- ERR 1 General error <Unspecified source> gpg: error searching keyserver: General error gpg: keyserver search failed: General error gpg: DBG: chan_3 -> BYE gpg: DBG: [not enabled in the source] stop gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 gpg: secmem usage: 0/65536 bytes in 0 blocks $ Thanks Norbert -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.10.0 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnupg depends on: ii gnupg-agent 2.1.18-6 ii libassuan0 2.4.3-2 ii libbz2-1.0 1.0.6-8.1 ii libc6 2.24-10 ii libgcrypt20 1.7.6-1 ii libgpg-error0 1.26-2 ii libksba8 1.3.5-2 ii libreadline7 7.0-2 ii libsqlite3-0 3.16.2-3 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages gnupg recommends: ii dirmngr 2.1.18-6 ii gnupg-l10n 2.1.18-6 Versions of packages gnupg suggests: pn parcimonie <none> pn xloadimage <none> -- no debconf information
--- End Message ---
--- Begin Message ---On 2017-05-17 David Rabel <[email protected]> wrote: > On 17.05.2017 16:03, Daniel Kahn Gillmor wrote: [...] >> if you're able to reproduce it, can you show me the output of: >> gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye > I will. Let's close this. It is unlikely we will get more info on this 8 years later. cu Andreas
--- End Message ---
