- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 23 2024
I've moved the gpg task to a new ticket, T7133: Add feature to load designated revoker from LDAP
The Kleopatra task is obsolete, as it was noticed that the proposed option is already in gpg and should not be implemented twice.
Sorry, no. The change is too large to back port it w/o risking a regression. As mentioned in T6481#170366 I don't consider this a bug. We are anyway working towards version 2.6 which will be the next LTS version.
May 22 2024
I think it would be cleaner to create a separate ticket for making gpg fetch the requested key from LDAP.
Any chance this could also be fixed in the 2.2.x series, where it seems to have been introduced in 2.2.42?
Although it is implemented in gnupg-2.2 we should add another feature: Iff this option is configured, gpg shall try to load the requested key from LDAP in the same manner as it does for a trusted-key.
This should not be configured in Kleopatra but an option to gpg because this is a core crypto functionality. Thus is now a gpg task.
this has been implemented since february 2023 in all gnupg versions