| Summary: | LDAP x509 lookup fails | ||
|---|---|---|---|
| Product: | [Applications] kleopatra | Reporter: | Dave Loyall <dave> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | dave, mutz |
| Priority: | NOR | ||
| Version: | 2.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | ||
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |
Verisign operates a keyserver. I have a public key in there. Normally I can grab it by using this command: $ ldapsearch -x -h directory.verisign.com cn="david loyall" (that's /usr/bin/ldapsearch from openldap.org...) I haven't been able to pull this public key down using Kleopatra. Reproducible: Always Steps to Reproduce: 1. Open Kleopatra for the first time. Configure a directory service. Scheme: ldap Server name: directory.verisign.com Server Port: 389 Base DN: X.509: true OpenPGP: false 2. Use the Lookup Certificates On Server button on the main toolbar. Search criteria: cn="david loyall" (I also tried various other criteria.) 3. No results. Actual Results: No results found. Expected Results: The key might not be the right type, but I think that we're not even talking to the keyserver correctly. This appears in the log immediately after I click "search". 2015-02-18 15:40:29 gpg[8344] enabled debug flags: packet mpi cipher filter iobuf memory cache memstat trust hashing extprog cardio assuan 2015-02-18 15:40:29 gpg[8344] no keyserver known (use option --keyserver) 2015-02-18 15:40:29 gpg[8344] keyserver search failed: Syntax error in URI However, the UI doesn't seem to "finish" immediately... FYI.