Known Issues - open-eid/chrome-token-signing GitHub Wiki
Known Issues
Windows:
bug/ux: PIN dialog is still shown after PIN has been blocked (You can still enter PIN even though your PIN is blocked). The only option is pressing cancel (IB-2069).
with CNG/CAPI interface language selection from https://github.com/open-eid/hwcrypto.js does not affect language on those interface PIN dialogs, instead is language what is defined in crypto service provider (IB-2532)
Resolved issues
Windows:
bug: if PIN gets blocked then "technical error" is returned instead of notifying the user (IB-3836)
bug/ux: If a short pin, less than 4 numbers long, is entered, then the dialog shows that you still have 3 tries left even after the card has been blocked (IB-3837)
Wishlist
Support for IFrames
Manifest file (and native messaging host) name ee.ria.esteid.json to be changed to token.signing.json
The origin of the request MUST be made visible to the user in all GUI windows of the native host (rationale: the window is disconnected from the related browser window)
Non-critical (SHOULD/MAY) informational dialog windows SHOULD be omitted if "quiet": true is in the request
If there is just a single suitable certificate, a "nice" window with information should be used instead of the list.
PIN dialog window icon. As far as we know it's not possible to change the Windows CAPI/CNG dialog icon.
Wishlist for PKCS#11:
OSX/Linux: if pin_blocked then no dialog is shown
OSX GUI: PIN dialog should be prettier, without the unnecessary error space above if no errors are shown, and less space between the input and buttons. (one possible solution is https://github.com/depth42/AutolayoutExtensions)
Windows PKCS#11 language selection support in addition to English
Wishlist for the extension:
Documenting the peculiarities of adding and removing the extension
Documenting the extension API
Support for Opera browser (should be doable, because it's a Chrome fork)