Although the list of readers is very helpful, we should eventually provide a dropdown combo box to select the reader. Not as important as the list but should be done as time permits.
Description
Description
Revisions and Commits
Revisions and Commits
| rLIBKLEO Libkleo | |||
| rLIBKLEO88576f47900a Add custom drop down box for configuring the reader-port option | |||
| rLIBKLEO34ba6f99cc23 Add a helper for splitting a std::string | |||
| rLIBKLEO5b3e58658cd7 Add function for retrieving a list of available smart card readers | |||
| rLIBKLEObe41844d93d7 Add functions for communicating with the GnuPG agent | |||
| rKLEOPATRA Kleopatra | |||
| rKLEOPATRA2d0972040bae Use getReaders() from libkleo to get the list of smart card readers | |||
| rKLEOPATRAdc9c7b62e23e Port to Assuan::send*Command functions in libkleo | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | • ikloecker | T5662 Kleopatra: Show a list of detected card readers | ||
| Resolved | • ebo | T5666 Create dropdown box for the reader-port option. |
Event Timeline
Comment Actions
Configuration dialog with reader-port drop down:
- The first entry Default reader will simply remove the reader-port option.
- The last entry Custom entry allows the user to enter an arbitrary value. It also preserves the currently configured value in case the configured reader is currently unplugged.
- The other entries list the currently available readers (as reported by scdaemon).
The first reader is a GnuK which has a nice USB device serial number. The other two are the reader that is built-in in my ThinkPad and a YubiKey. Both readers lack a USB device serial number which makes it difficult to know which reader to select. Moreover, I think it will make it impossible to select a specific YubiKey in case two identical YubiKeys are inserted because both YubiKeys will have identical reader IDs. I guess the users will have to resort to the numerical port number.
What should Kleopatra do?
Comment Actions
The distinction between reader and card is not easy and PS/SC is also not helpful here. The user needs to resort to trial and error. With 2.3 things are much easier because we do not need to select the reader anymore.
Kleopatra can't do much here and I think this is okay.