Closed horakivo closed 3 years ago
Project requires that Token is on Hardware device or smartcard.
Well mini.LECTOR-S is hardware device which which contains token. Can you explain your answer more?
Then I wonder why the provider minidriver/CSP does not expose the hardware flags? Can you provide some info about its middleware?
About middleware? I am not sure where to get info about middleware.. Will this info help? https://prnt.sc/vgkqpe
Does device manager list "smart card reader" and "smart card" drivers?
It just list "smart card reader". Took a screenshot. https://prnt.sc/vgl8kb
Hmm intresting can you produce logs with ole and new version of chrome token signing https://github.com/open-eid/chrome-token-signing/wiki/DeveloperTips#logging
non-working version.txt working version.txt
Here are logs
I really don't know why this device claims that it is not hardware token. Right now there is only solution to comment out the check. Project scope is to only allow sign with hardware tokens.
Closing this issue because currently there are no plans to allow signing with software token.
We are using mini.LECTOR-S token to sign and it doesnt work with the last versions. I have build all the versions to find the last working version which is v1.0.7.
EDIT: I did some digging and I found out that the commit: 757d8e3f4b68283c926ca0fced64a253120364b6 break the signing module. To be more precise it ends in condition if ((type & (NCRYPT_IMPL_HARDWARE_FLAG | NCRYPT_IMPL_REMOVABLE_FLAG)) == 0) where in my case type is 0.
I dont know a lot about signing, but can someone explain why the case was changed?
Thanks!