GNOME Bugzilla – Bug 401655
Could not publish to ldap://keyserver.pgp.com
Last modified: 2018-08-03 19:09:48 UTC
Error on sync Couldn't publish keys to server: ldap://keyserver.pgp.com entry has no objectClass attribute
pgp.com's keyservers may be running their own protocol. If they finally switched their beta key server to their primary we may not be able to fix this. Only if publishing to all ldap keyservers failed would this be a blocker.
Can duplicate. Would be nice to make this work. Will look further into it.
This is still an issue with 2.23.92. Any chance of fixing?
I got half way through fixing this, just now, but ran into a wall. There is indeed a new keyserver style, since they must be too lazy to maintain their old one. One needs to retrieve the server information completely differently (which I've implemented) and needs to send keys to the server in a more complex manner. The problem is that the new way of sending keys to the server involves accessing an LDAP DN based on the keys specific keyid. At that point in seahorse we don't have access to that information, but just to the raw armored key data. So this would need some refactoring of things in order to get it to work.
*** Bug 553845 has been marked as a duplicate of this bug. ***
*** Bug 565141 has been marked as a duplicate of this bug. ***
Has the needed refactoring been put on some type of road map or release goal?
No it hasn't and I haven't had time to work on it. Are you interested in picking this up?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/17.