Bug 378775 - kleopatra: search ignores the 'Name' entry of x509 certificats, fails to match '-' and does not show hits in collapsed x509 chains
Summary: kleopatra: search ignores the 'Name' entry of x509 certificats, fails to matc...
Status: RESOLVED FIXED
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 2.3.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-14 12:38 UTC by Achim Bohnet
Modified: 2017-04-18 12:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 17.04


Attachments
example data set used in bug description (79.81 KB, image/png)
2017-04-14 12:38 UTC, Achim Bohnet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Achim Bohnet 2017-04-14 12:38:04 UTC
Created attachment 105023 [details]
example data set used in bug description

Attached screenshot is used to illustrate the bugs:

1) Search for my name 'achim' only shows the opengpg keys, not the my x509 key
   Should list x509 key too.   Searching for 'Telekom' finds nothing.

2) Search for mpg-ca should match due to the e-mail of 'MPG CA' in my cerificate chain. Bug: search result is empty. 

3) By default X509 chains are not expanded, only the Root cert is shown. If I search for something that matches in the X509 trust chain, the chain is not expanded to show the matching entry.
Comment 1 Achim Bohnet 2017-04-15 13:47:05 UTC
Same problem when I turn off: View -> Hierarchical Ceritificate List

Search e.g. for my first name and my X509 cert isn't shown. Only my openpgp certs.
Comment 2 Andre Heinecke 2017-04-18 12:51:02 UTC
Thanks for your reports.

Indeed the search problems 1 / 2 are a regression, we now matches any part of the DN additionally to E-Mails.

> 3) By default X509 chains are not expanded, only the Root cert is shown. If I 
> search for something that matches in the X509 trust chain, the chain is not 
> expanded to show the matching entry.

This is a bit unrelated and was always the case but I agree. I've opened bug 378924 to track this separately as I want to close this bug with fixed search.