Fixed for gpg < 2.3. To make the fix also work for gpg 2.3, T5462: gpgconf: Make gpg/keyserver option available again needs to be fixed.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 23 2021
Jun 22 2021
Jun 21 2021
Jun 17 2021
Jun 11 2021
Jun 10 2021
Jun 8 2021
Jun 7 2021
Jun 4 2021
Jun 2 2021
Jun 1 2021
Yes, --x509server does better convey the semantics of this option.
May 31 2021
Now, it is still time to change the name of the new option "--ldapserver". "--x509server" maybe?
In T5404#146459, @werner wrote:I implemented the new format in 2.2 but we need to discuss how to handle this in gpgconf.
May 28 2021
Yes. This is not a backend issue. Kleopatra can determine if it has connection to the keyserver but the issue is about that Kleopatra should determine that and indicate that.
May 27 2021
Just search for something.
Yeah, but cbiedl's issue is about something like that in Kleopatra for "users".
May 26 2021
You can easily do this with gpg-connect-agent
I implemented the new format in 2.2 but we need to discuss how to handle this in gpgconf.
Fixed. Kleopatra no longer tries to parse the keyserver option and treats it as simple text (instead of as URL).
May 25 2021
May 20 2021
Current look without public keys:
May 19 2021
Having a fallback in Kleopatra makes sense because very old HKP keyservers don't return the fingerprint and LDAP keyservers not using the modernized schema do neither.
I just talked with werner about that and he told me that GnuPG can return the fingerprint. And I also mentioned to him that kleopatra really assumes that a Fingerprint is always set for a valid key object.
Should have linked the commit with a patch for Gpg4win here: 22bc52775bdb I mostly needed that as an immediate fix for someone testing with ldap servers a lot.
May 17 2021
May 12 2021
May 10 2021
May 6 2021
May 4 2021
May 3 2021
The error code is: No Readers Available. With the latest version you should have seen that string.
I had a similar issue in Windows 10 too. In my case, the issue occurs only when my home path has non-ASCII characters. After I changed home path it works well.
In T5359#145741, @werner wrote:Can you please clarify this point: If you run on Unix with --disable-ccid-driver, do you get the same behavior as on Windows?
Can you please clarify this point: If you run on Unix with --disable-ccid-driver, do you get the same behavior as on Windows?
Apr 30 2021
I have disabled this on Windows. Once "SCD DEVINFO --watch" works reliably on Windows, we can reenable the DeviceInfoWatcher on Windows.
Hi Ingo,
Apr 29 2021
Apr 28 2021
Should be mostly done. What's missing is selection of groups in the approval dialog. Groups are not (yet) supported by the KeySelectionCombo.