This is based off #24 and removes support for SRV DNS records. SRV records are used to advertise alternative services in a domain are available, such as LDAP, XMPP or SIP. The SKS Keyserver HKP Pools use them to indicate the quality of a keyserver that is then accessed via http/https by their weights.
Although interesting, the use of SRV weights to optimize the keyserver pool access is highly unorthodox for HTTP/HTTPS load balancing. I understand it is an attempt to eliminate the middle-man, but it is not clear what the threat model here is that motivates these complexities.
This is based off #24 and removes support for SRV DNS records. SRV records are used to advertise alternative services in a domain are available, such as LDAP, XMPP or SIP. The SKS Keyserver HKP Pools use them to indicate the quality of a keyserver that is then accessed via http/https by their weights.
I removed support for SRV DNS records from NeoPG:
If there ever will be curl support for it, we might reconsider this.