Page MenuHome GnuPG
Feed Advanced Search

Wed, Sep 22

werner closed T5618: GPG Key Server Doesn´t Work as Resolved.

Ah well, Kleopatra has a GUI to set the keyserver - that is probably easier to use.

Wed, Sep 22, 7:17 PM · Support, FAQ, Keyserver, gpg4win

Sep 7 2021

FierzvID added a member for Keyserver: FierzvID.
Sep 7 2021, 10:42 PM
FierzvID added a watcher for Keyserver: FierzvID.
Sep 7 2021, 10:41 PM

Aug 25 2021

werner triaged T5527: keys.gnupg.net is obsolete as Low priority.
Aug 25 2021, 4:31 PM · Keyserver, FAQ, Documentation
werner closed T5552: Key information loading is sometimes very slow. Suspected that the problem originated from gnupg. as Resolved.

Okay, I close this as a keyserver infrastructure problem. Feel free tore-open if you get other infos.

Aug 25 2021, 4:30 PM · FAQ, Keyserver, gnupg

Aug 13 2021

werner changed the edit policy for Keyserver.
Aug 13 2021, 11:06 PM

Jul 28 2021

werner removed a parent task for T4694: manage first-party attestations: Restricted Maniphest Task.
Jul 28 2021, 3:20 PM · Keyserver, Feature Request

Jul 15 2021

brent0919 added a comment to U11 Jacob Smith.

[[ URL | foreach ($list as $item) {

work_miracles($item);

} ]]

Jul 15 2021, 6:55 PM · Keyserver

Jun 21 2021

Valodim added a comment to T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.

The sks pool is now officially gone.

Jun 21 2021, 11:50 PM · gnupg, Keyserver

Feb 2 2021

werner closed T5105: can't find users with Kleopatra when press "Look up on server" as Resolved.

Please do not repeat you question, this won't give you anymore attention. Read my comment above and please ask on a mailing list etc.

Feb 2 2021, 4:00 PM · Support, kleopatra, Keyserver
fabior added a comment to T5105: can't find users with Kleopatra when press "Look up on server".

Good morning,

Feb 2 2021, 12:38 PM · Support, kleopatra, Keyserver

Jan 28 2021

Valodim added a comment to T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.

The last server of the HKPS pool dropped off for several hours yesterday, during which hkps.pool.sks-keyservers.net could not be resolved.

Jan 28 2021, 11:17 AM · gnupg, Keyserver

Jan 5 2021

wiktor-k added a comment to T4694: manage first-party attestations.

For the context of all subscribed parties I think Werner refers to what Hockeypuck is doing: https://lists.gnupg.org/pipermail/gnupg-users/2020-December/064441.html

Jan 5 2021, 10:45 AM · Keyserver, Feature Request
werner lowered the priority of T4694: manage first-party attestations from High to Low.

Meanwhile there are simpler ideas and code on how to do only authenticated uploads. Thus lowering the prio.

Jan 5 2021, 10:41 AM · Keyserver, Feature Request
werner triaged T5072: Keyserver presents the expiry date incorrectly as Low priority.
Jan 5 2021, 9:37 AM · Keyserver
werner triaged T5105: can't find users with Kleopatra when press "Look up on server" as Low priority.

(Reporter has problems running his own keyserver and accessing it.)

Jan 5 2021, 9:28 AM · Support, kleopatra, Keyserver

Dec 4 2020

Valodim added a comment to T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.

Perhaps of interest for this issue: the HKPS pool has consisted of only a single server for a couple of months now.

Dec 4 2020, 1:07 PM · gnupg, Keyserver

Nov 27 2020

werner lowered the priority of T3392: keyserver default should include pool onionbalance hkp://jirk5u4osbsr34t5.onion from Normal to Wishlist.
Nov 27 2020, 5:39 PM · Keyserver, Feature Request, dirmngr

Oct 19 2020

fabior added a comment to T5105: can't find users with Kleopatra when press "Look up on server".

My sks keyserver is in Linux Ubuntu 18.04 LTS. As a client I'm using windows 10 and gpg4win is 3.1.13.

Oct 19 2020, 6:12 PM · Support, kleopatra, Keyserver
werner removed Version on T5105: can't find users with Kleopatra when press "Look up on server".
Oct 19 2020, 1:27 PM · Support, kleopatra, Keyserver
werner edited projects for T5105: can't find users with Kleopatra when press "Look up on server", added: Keyserver, kleopatra; removed gpg4win.

Are you on Windows or Linux? What version of Kleopatra or Gpg4win are you using?

Oct 19 2020, 1:27 PM · Support, kleopatra, Keyserver

Sep 17 2020

Georg3 created T5072: Keyserver presents the expiry date incorrectly in the S1 Public space.
Sep 17 2020, 10:35 AM · Keyserver

Aug 12 2020

auth0rize created U11 Jacob Smith in the S1 Public space.
Aug 12 2020, 8:11 AM · Keyserver

Jul 9 2020

werner closed T4856: GPG: Key Exchange Put public OpenPGP key into signature as Resolved.
Jul 9 2020, 1:15 PM · Feature Request, gpgol, Keyserver, gnupg

Mar 14 2020

werner added a comment to T4856: GPG: Key Exchange Put public OpenPGP key into signature.

I think that this chnage is useful enough to be backported to 2.2. Done that.

Mar 14 2020, 8:14 PM · Feature Request, gpgol, Keyserver, gnupg

Mar 13 2020

werner changed the status of T4856: GPG: Key Exchange Put public OpenPGP key into signature from Open to Testing.
Mar 13 2020, 5:29 PM · Feature Request, gpgol, Keyserver, gnupg
werner added a comment to T4856: GPG: Key Exchange Put public OpenPGP key into signature.

You can test it now out using GnuPG master: Just add --include-key-block and you can then verify using an empty keyring. Currently --auto-key-retrieve is not needed but we need to think on how we can enable or disable this during verification.

Mar 13 2020, 5:28 PM · Feature Request, gpgol, Keyserver, gnupg
werner added a project to T4856: GPG: Key Exchange Put public OpenPGP key into signature: Feature Request.
Mar 13 2020, 1:17 PM · Feature Request, gpgol, Keyserver, gnupg

Mar 10 2020

Valodim added a comment to T4856: GPG: Key Exchange Put public OpenPGP key into signature.

ftr, here is the thread I had in mind but couldn't recall above. @aheinecke is that your thinking, or a more pgp/mime bound mechanism as @dkg assumed?

Mar 10 2020, 5:50 PM · Feature Request, gpgol, Keyserver, gnupg
dkg added a comment to T4856: GPG: Key Exchange Put public OpenPGP key into signature.

@wiktor-k, "just extend the spec" doesn't necessarily work with existing clients, which might be surprised to find unexpected packets in the signature section of an e-mail. It seems more likely to me that they'd be able to handle (meaning: ignore) an unknown subpacket (as long as it's well-formed) than to handle additional packets. But all of these surmises require testing with existing clients, of course. Has anyone done any of that testing?

Mar 10 2020, 3:19 PM · Feature Request, gpgol, Keyserver, gnupg
wiktor-k added a comment to T4856: GPG: Key Exchange Put public OpenPGP key into signature.

This is a nice idea and although it overlaps with Autocrypt it has other uses too: for example verification of signed files that can be vastly simplified (just get the file and the signature, no key fetching needed, downside: the key attached to the signature could be stale).

Mar 10 2020, 10:04 AM · Feature Request, gpgol, Keyserver, gnupg
dkg added a comment to T4856: GPG: Key Exchange Put public OpenPGP key into signature.

Ah, thanks for pointing out the subpacket option (i guess it could be hashed or unhashed). i don't think any of the subpackets currently defined in RFC4880 supports this use case -- but i guess you could mint a new one, or use a notation.

Mar 10 2020, 1:22 AM · Feature Request, gpgol, Keyserver, gnupg
Valodim added a comment to T4856: GPG: Key Exchange Put public OpenPGP key into signature.

Werner said that it's possible in OpenPGP to also put the pubkey into the signature. (...) The nice advantage is that this will also work for files.

Mar 10 2020, 12:31 AM · Feature Request, gpgol, Keyserver, gnupg

Mar 9 2020

dkg added a comment to T4856: GPG: Key Exchange Put public OpenPGP key into signature.

Hi @aheinecke, thanks for thinking about this, and thanks for tagging me here too. I'm definitely interested.

Mar 9 2020, 9:53 PM · Feature Request, gpgol, Keyserver, gnupg

Feb 26 2020

aheinecke created T4856: GPG: Key Exchange Put public OpenPGP key into signature.
Feb 26 2020, 12:33 PM · Feature Request, gpgol, Keyserver, gnupg
aheinecke added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

But searching on Keyservers is also in my opinion not a common use case for Kleopatra users.

Thanks for engaging constructively.

Feb 26 2020, 12:03 PM · Feature Request, Keyserver, dirmngr

Feb 21 2020

dkg added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

In T4513#132770, @aheinecke wrote:

Werner could you maybe at least check for an internet connection, I don't know how to do it on Linux but on Windows it's easy because windows has API for that.

Feb 21 2020, 6:33 PM · Feature Request, Keyserver, dirmngr

Feb 19 2020

Valodim added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

But searching on Keyservers is also in my opinion not a common use case for Kleopatra users.

Feb 19 2020, 6:43 PM · Feature Request, Keyserver, dirmngr
werner added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

and by that bypassing all key source tracking as done by gpg. In any case searching by name or mail address on a keyserver should not be done - at least not by a GUI tool as used by non experienced users.

Feb 19 2020, 4:34 PM · Feature Request, Keyserver, dirmngr
patrick added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

I agree that this is a tricky problem, but it should really be improved.

Feb 19 2020, 4:05 PM · Feature Request, Keyserver, dirmngr
werner added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

The problem is not to check whether there is a connection but on how to decide whether something is a pool or an explictly added single keyserver and how often should we try to connect or read from it. Without marking hosts as dead the auto search features won't work well.

Feb 19 2020, 1:30 PM · Feature Request, Keyserver, dirmngr
aheinecke added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

@Valodim probably not so much as dirmngr might behave differently and not mark hosts as dead.

Feb 19 2020, 1:17 PM · Feature Request, Keyserver, dirmngr
werner added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

The proper solution is of course to use pkill instead of killall. SCNR.

Feb 19 2020, 12:43 PM · Feature Request, Keyserver, dirmngr
Valodim updated subscribers of T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

I can attest to the "growing bit of popular lore": Roughly half the support requests I get to support@keys.openpgp.org boil down to an exchange of "it just doesn't work with a 'general error' message" -> "try killall dirmngr" -> "that did it". I have heard similar stories from @patrick from Enigmail users, and more than once heard people applying poweruser trickery like "I just have killall dirmngr in my resume.d".

Feb 19 2020, 11:37 AM · Feature Request, Keyserver, dirmngr

Nov 25 2019

werner closed T4165: Dirmngr: Ipv6 causes network failure if Ipv6 can't be reached, a subtask of T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default, as Resolved.
Nov 25 2019, 10:17 PM · gnupg, Keyserver
werner closed T4165: Dirmngr: Ipv6 causes network failure if Ipv6 can't be reached as Resolved.

Unusable v6 interfaces are now detected on Windows and then not used.

Nov 25 2019, 10:17 PM · Keyserver, Feature Request, dirmngr
werner closed T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned as Resolved.
Nov 25 2019, 10:15 PM · Keyserver, gnupg (gpg22), Bug Report

Nov 20 2019

werner lowered the priority of T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned from Normal to Wishlist.
Nov 20 2019, 8:58 AM · Keyserver, gnupg (gpg22), Bug Report

Nov 7 2019

werner moved T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned from Backlog to For next release on the gnupg (gpg22) board.
Nov 7 2019, 3:15 PM · Keyserver, gnupg (gpg22), Bug Report
werner changed the status of T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned from Open to Testing.
Nov 7 2019, 3:14 PM · Keyserver, gnupg (gpg22), Bug Report

Oct 25 2019

mgorny added a comment to T4444: dirmngr fails with keyservers specified by IP without rDNS; reported as dead host or uses wrong Host header.

Ping.

Oct 25 2019, 10:54 AM · Keyserver, dns, dirmngr, Bug Report

Oct 24 2019

dkg added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

There is a growing bit of popular lore in the GnuPG community that "when keyserver operations fail, you solve that problem with killall dirmngr." I believe this suggestion is potentially damaging (the long-running daemon may be in the middle of operations for a client that you don't know about), but i suspect it is circulating as advice because it resolves the situation outlined in this ticket. For whatever ephemeral reason, dirmngr gets stuck, and fails to notice that this situation has resolved itself.

Oct 24 2019, 5:39 PM · Feature Request, Keyserver, dirmngr

Jul 18 2019

dkg added a comment to T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned.

I'm aware of you releasing an RC for comments, and i apologize for not catching this particular case earlier. As you know from T4607, i was even advocating for it. i didn't understand the full implications of the "import-then-clean" approach at the time, and was thinking it would only apply to the incoming material, not the stored material.

Jul 18 2019, 4:26 PM · Keyserver, gnupg (gpg22), Bug Report
werner added a comment to T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned.

The code has comments why we do a first clean_key on the imported keyblock.

Jul 18 2019, 11:07 AM · Keyserver, gnupg (gpg22), Bug Report
dkg added a comment to T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned.

i've merged a variant of rGbe99eec2b105eb5f8e3759147ae351dcc40560ad into the GnuPG packaging in debian unstable as of version 2.2.17-3 to avoid the risks of data loss and signature verification failures. I'll revert it if i see the concern addressed upstream.

Jul 18 2019, 12:17 AM · Keyserver, gnupg (gpg22), Bug Report

Jul 16 2019

dkg added a comment to T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned.

that pseudocode is strange to me -- it looks like you have (two) duplicate calls to clean_key (imported_keyblock) (though maybe i just don't know what .... means in this pseudocode).

Jul 16 2019, 6:36 PM · Keyserver, gnupg (gpg22), Bug Report
werner triaged T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned as Normal priority.
Jul 16 2019, 8:25 AM · Keyserver, gnupg (gpg22), Bug Report
werner added a comment to T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned.

You are partly right. I missed that we also do clean the original keyblock while updating a key. The code is

Jul 16 2019, 8:17 AM · Keyserver, gnupg (gpg22), Bug Report

Jul 15 2019

dkg added a comment to T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned.

I think dropping import-clean from the default keyserver options is the right way to go. It is not clear what additional benefit import-clean provides given that we are already using self-sigs-only. And the idea of non-additive behavior to the local keyring when pulling from a keyserver is a deeply surprising change for multiple users i've talked to.

Jul 15 2019, 10:35 PM · Keyserver, gnupg (gpg22), Bug Report
dkg created T4628: new import-clean default for keys from keyservers modifies the local keyring when anything is returned.
Jul 15 2019, 7:09 PM · Keyserver, gnupg (gpg22), Bug Report
werner triaged T4617: Odd behavior for HTTP(S) scheme in --keyserver config as Low priority.
Jul 15 2019, 8:16 AM · Documentation, Keyserver, dirmngr

Jul 14 2019

dkg added a project to T4617: Odd behavior for HTTP(S) scheme in --keyserver config: Documentation.
Jul 14 2019, 6:49 PM · Documentation, Keyserver, dirmngr

Jul 10 2019

Valodim updated subscribers of T4617: Odd behavior for HTTP(S) scheme in --keyserver config.

Ah, that makes sense, good catch. Seems this is just an issue of documentation, then.

Jul 10 2019, 6:20 PM · Documentation, Keyserver, dirmngr
dkg added projects to T4617: Odd behavior for HTTP(S) scheme in --keyserver config: dirmngr, Keyserver.
Jul 10 2019, 6:11 PM · Documentation, Keyserver, dirmngr
Valodim added a comment to T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.

We should put it of the agenda od the Brussesl summit in 3 weeks. I have a few ideas what we can do in gpg.

Jul 10 2019, 4:36 PM · gnupg, Keyserver

Jul 4 2019

werner edited projects for T4512: gpg's --keyserver option should be more robustly deprecated, added: gnupg (gpg23); removed gnupg (gpg22), dirmngr.

Given the recent problems with the keyservers, I expect that the keyserver feature will go away anyway and thus I do not think we will put any more effort into this. Thus I re-tag this as gpg 2.3.

Jul 4 2019, 5:15 PM · gnupg (gpg23), Documentation, Keyserver, Bug Report

Jun 18 2019

dkg added a comment to T4512: gpg's --keyserver option should be more robustly deprecated.

If we only need it for backward compatibility, then the configuration in gpg.conf should *not* be overriding the preferred, forward-looking form of the configuration (in dirmngr.conf). If it is low priority to fix this, then there will be a generation of GnuPG users and toolchains which deliberately configure the value in gpg.conf instead of dirmngr.conf because they'll know that's the more robust way to do it.

Jun 18 2019, 2:56 AM · gnupg (gpg23), Documentation, Keyserver, Bug Report

Jun 8 2019

werner triaged T4512: gpg's --keyserver option should be more robustly deprecated as Low priority.

We need --keyserver in gpg for just one reason: backward compatibility.

Jun 8 2019, 10:40 AM · gnupg (gpg23), Documentation, Keyserver, Bug Report
dkg reopened T4512: gpg's --keyserver option should be more robustly deprecated as "Open".

thanks for fixing that error message, @werner. As @Valodim points out in discusson about hagrid, a gpg.conf keyserver option (deprecated according to the documentation) overrides the dirmngr.conf keyserver option (not deprecated according to the documentation.

Jun 8 2019, 5:29 AM · gnupg (gpg23), Documentation, Keyserver, Bug Report

May 27 2019

werner added a comment to T4165: Dirmngr: Ipv6 causes network failure if Ipv6 can't be reached.

I doubt that we are going to implement this.

May 27 2019, 6:15 PM · Keyserver, Feature Request, dirmngr

May 17 2019

werner triaged T4444: dirmngr fails with keyservers specified by IP without rDNS; reported as dead host or uses wrong Host header as Normal priority.
May 17 2019, 6:47 PM · Keyserver, dns, dirmngr, Bug Report

May 15 2019

werner closed T4466: Clean up --keyserver documentation in gpg(1) as Resolved.

Thanks

May 15 2019, 9:20 AM · Keyserver, gnupg (gpg22), dirmngr, Documentation
werner claimed T4466: Clean up --keyserver documentation in gpg(1).
May 15 2019, 9:06 AM · Keyserver, gnupg (gpg22), dirmngr, Documentation

May 14 2019

werner triaged T4513: dirmngr should try the configured keyservers anyway even if they are all dead as Normal priority.
May 14 2019, 10:09 AM · Feature Request, Keyserver, dirmngr
werner closed T4512: gpg's --keyserver option should be more robustly deprecated as Resolved.

I removed this specialized error message. Thanks for reporting.

May 14 2019, 8:38 AM · gnupg (gpg23), Documentation, Keyserver, Bug Report
dkg updated the task description for T4512: gpg's --keyserver option should be more robustly deprecated.
May 14 2019, 7:42 AM · gnupg (gpg23), Documentation, Keyserver, Bug Report
dkg edited projects for T4466: Clean up --keyserver documentation in gpg(1), added: dirmngr, gnupg (gpg22), Keyserver; removed gnupg.
May 14 2019, 7:40 AM · Keyserver, gnupg (gpg22), dirmngr, Documentation
dkg added a comment to T4513: dirmngr should try the configured keyservers anyway even if they are all dead.

This is particularly bad for users who have manually specified a given keyserver in dirmngr.conf, because even a transient failure in that keyserver will prevent them from any future keyserver requests until dirmngr decides that the "death" has worn off.

May 14 2019, 1:00 AM · Feature Request, Keyserver, dirmngr
dkg created T4513: dirmngr should try the configured keyservers anyway even if they are all dead.
May 14 2019, 12:54 AM · Feature Request, Keyserver, dirmngr
dkg created T4512: gpg's --keyserver option should be more robustly deprecated.
May 14 2019, 12:49 AM · gnupg (gpg23), Documentation, Keyserver, Bug Report

Apr 1 2019

robbat2 added a comment to T4444: dirmngr fails with keyservers specified by IP without rDNS; reported as dead host or uses wrong Host header.

HTTP/1.1 spec, RFC 7230, Section 5.4, paragraph 2:
https://tools.ietf.org/html/rfc7230#section-5.4

Apr 1 2019, 8:24 PM · Keyserver, dns, dirmngr, Bug Report
werner added a comment to T4444: dirmngr fails with keyservers specified by IP without rDNS; reported as dead host or uses wrong Host header.

Please be so kind and point me to the specs stating that you should put the IP address into Host:

Apr 1 2019, 8:01 PM · Keyserver, dns, dirmngr, Bug Report
robbat2 added a comment to T4444: dirmngr fails with keyservers specified by IP without rDNS; reported as dead host or uses wrong Host header.

It's up to GPG to send the Host header that shows the user's intent.

Apr 1 2019, 6:20 PM · Keyserver, dns, dirmngr, Bug Report
werner added a comment to T4444: dirmngr fails with keyservers specified by IP without rDNS; reported as dead host or uses wrong Host header.

So in short you want:

  1. Allow to specify a keyserver by IP without any DNS lookups.
  2. When connecting via IP use the IP address for Host:.
Apr 1 2019, 12:55 PM · Keyserver, dns, dirmngr, Bug Report

Mar 31 2019

robbat2 created T4444: dirmngr fails with keyservers specified by IP without rDNS; reported as dead host or uses wrong Host header.
Mar 31 2019, 10:35 PM · Keyserver, dns, dirmngr, Bug Report

Mar 13 2019

wuximeniyu added a comment to T4165: Dirmngr: Ipv6 causes network failure if Ipv6 can't be reached.

There is a solution for it:

Mar 13 2019, 9:55 PM · Keyserver, Feature Request, dirmngr

Feb 9 2019

kristianf closed T4354: dirmngr should send "fingerprint=on" to keyservers as Resolved.

So, the keyserver operator had thrown in a hockeypuck server in the pool, causing this.. While the keyserver remains in the exclude list until confirmation it has been resolved, that explains the behavior and it has been made clear that separate software needs to use different names in the future.

Feb 9 2019, 8:43 PM · dirmngr, Keyserver, Bug Report

Feb 4 2019

werner updated subscribers of T4354: dirmngr should send "fingerprint=on" to keyservers.

@kristianf we talked about this on Saturday evening. Would you be so kind and have a quick look at the problem with the hu server?

Feb 4 2019, 5:45 PM · dirmngr, Keyserver, Bug Report

Feb 1 2019

steve added a comment to T4354: dirmngr should send "fingerprint=on" to keyservers.

Hi Werner and thanks for looking into this.

Feb 1 2019, 10:32 AM · dirmngr, Keyserver, Bug Report

Jan 30 2019

werner edited projects for T4354: dirmngr should send "fingerprint=on" to keyservers, added: Keyserver, dirmngr; removed Feature Request.

According to sks-keyservers.net both servers you mention run the very same software. Thus I would like to understand why you think they require the use of a legacy option.

Jan 30 2019, 3:22 PM · dirmngr, Keyserver, Bug Report

Oct 29 2018

werner triaged T4165: Dirmngr: Ipv6 causes network failure if Ipv6 can't be reached as High priority.

It actually tries several servers but we need to set a limit because we need to cope with longer timeouts. Do you suggest to toggle between v4 and v6 addresses? That is if a v6 address fails, first try the next v4 address and it that fails, another v6 address, etc.

Oct 29 2018, 9:41 AM · Keyserver, Feature Request, dirmngr

Oct 2 2018

werner added a comment to T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.

The problem is that the keyserver network is abused as free and
permanent data storage. We can't do much about it without larger
changes on the search capabilities of the keyservers. For more
information see the archives of the sks-devel list starting in July.

Oct 2 2018, 8:50 AM · gnupg, Keyserver

Oct 1 2018

aheinecke added a subtask for T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default: T4165: Dirmngr: Ipv6 causes network failure if Ipv6 can't be reached.
Oct 1 2018, 2:39 PM · gnupg, Keyserver
aheinecke triaged T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default as Normal priority.
Oct 1 2018, 10:24 AM · gnupg, Keyserver
aheinecke claimed T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.

Ok. I was not aware that HKPS should already have the highest quality.

Oct 1 2018, 10:23 AM · gnupg, Keyserver
kristianf added a comment to T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.

hkps pool really should be the most responsive, and it already requires clustered only servers for a couple of weeks to try to increase the responsiveness. Experience has shown that any keyserver with less than 3 nodes in a cluster should not be used towards end-users. But do you have any more debugging output as to the problem at hand?

Oct 1 2018, 10:19 AM · gnupg, Keyserver
aheinecke created T4163: hkps://hkps.pool.sks-keyservers.net has to many bad servers to be a good default.
Oct 1 2018, 9:40 AM · gnupg, Keyserver

Sep 11 2018

werner closed T2968: gpg --search: Connection closed in DNS as Resolved.

We assume that this has meanwhile been fixed.

Sep 11 2018, 10:34 AM · Info Needed, gnupg (gpg22), Bug Report, Debian, Keyserver, dirmngr

Aug 29 2018

werner added a project to T2968: gpg --search: Connection closed in DNS: Info Needed.

@elonsatoshi: Were you able to check this with 2.2.9 which has a fix for the resolver?

Aug 29 2018, 2:53 PM · Info Needed, gnupg (gpg22), Bug Report, Debian, Keyserver, dirmngr

Nov 19 2017

elonsatoshi added a comment to T2968: gpg --search: Connection closed in DNS.

You know... I think connman and DNS have something to do with this. Connman does some weird DNS thing. And it auto-generates /etc/resolv.conf to use localhost as the DNS server.

Nov 19 2017, 4:48 AM · Info Needed, gnupg (gpg22), Bug Report, Debian, Keyserver, dirmngr