Fix addition of new GPG keys to LDAP
Open, HighPublic


When a new key is being added to a ldap keyserver, dirmngr creates an LDAP object with only two attributes: pgpKey and pgpCertID. The rest of attributes is silently dropped. I have submitted a patch:


gray created this task.Apr 3 2019, 11:27 AM
werner triaged this task as High priority.Apr 5 2019, 9:07 AM
MCMic added a subscriber: MCMic.Apr 25 2019, 9:24 AM
werner added a subscriber: werner.Nov 11 2019, 6:30 PM

See also D475.

While looking at this I figured that ks-engine-ldap links in all the stuff we do not want (i.e. a second crypto library) and due to the way it has been ported from the old ldap keyserver helper it does not make use of our LDAP infrastructure. Our LDAP code shall use the wapper so that we don't run into linkage problems with libldap, avoid spreading the code with npth_unprotect/protect, and to have a working timeout for all ldap calls. I wonder why the stuff works at all.

werner edited projects, added gnupg (gpg23); removed gnupg.Nov 11 2019, 6:32 PM