Has now been backported to be released with 2.2.53
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Fri, Feb 13
Fri, Feb 13
• werner moved T7133: Add feature to load designated revoker from LDAP from Backlog to WIP on the vsd34 board.
• werner changed the status of T7133: Add feature to load designated revoker from LDAP from Open to Testing.
• werner moved T7333: Allow gpg to auto-upload a new own key to LDAP servers from Backlog to WIP on the vsd34 board.
• werner changed the status of T7333: Allow gpg to auto-upload a new own key to LDAP servers from Open to Testing.
• werner moved T7866: Allow separate LDAP keyserver for uploading from WIP to Done on the gnupg26 board.
• werner moved T7866: Allow separate LDAP keyserver for uploading from Backlog to WiP on the gnupg22 board.
• werner changed the status of T7866: Allow separate LDAP keyserver for uploading from Open to Testing.
Thu, Feb 5
Thu, Feb 5
It looks like we get a specific "Invalid public key algorithm" error from gpgme so that we can add helpful information with likely reasons to the error message.
I might add that we recently had a customer support contact where they had that error and asked how they could make using their S/MIME certificates work.
Jan 9 2026
Jan 9 2026
• werner moved T7866: Allow separate LDAP keyserver for uploading from QA to WIP on the gnupg26 board.
The behaviour might have changed a bit because of the ldap: prefix i use now, or i have missed this case the last time:
Given some cert on the "download" server, I can find it, if dirmngr.conf contains only the "download" server, or if the "download" server is listed first:
Independent of keyserver order in dirmngr.conf, --search-keys still offers keys from the upload server, but the download fails:
For "Although the upload server is used for upload, the gpg message still displays the first keyserver" see T8025
• werner edited projects for T6436: Double pinentry on change password, added: gnupg26; removed gnupg24.
That was fixed with 2.2.52 which fixed a bug in the fix done in 2.2.50 (see rG31fef13df1). Note that 2.2.48 to 2.2.50 had only internal releases.
Jan 8 2026
Jan 8 2026
• werner raised the priority of T6644: GnuPG: Allow non compliant signatures in compliance mode from Wishlist to Normal.
Jan 5 2026
Jan 5 2026
timegrid moved T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server from QA to Done on the gnupg26 board.
timegrid moved T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server from WIP to Done on the gpd5x board.
The problem was the keyserver configuration, which does not include a scheme (ldap:):
keyserver ldap.gnupg.test:389:uid=LordPrivySeal,ou=GnuPG Users,dc=gnupg,dc=test:pass:dc=gnupg,dc=test: