Closed SteffanDonal closed 1 year ago
Why do you think that the non-functioning EIDAuthenticate is related to the log message that GET_FEATURE_REQUEST is not supported?
This issue reports a similar error message https://github.com/OpenSC/OpenSC/issues/2155
It turns out, that you need to activate the OpenSC minidriver by registering the ATR in the regestry so that OpenSC actually gets loaded for your card.
Hey @frankmorgner
Thanks for the response; I've done some more digging on my end and tried a physical reader plugged directly into the PC, and I'm still getting this issue (and others) from all software I'm attempting to use.
When I posted the issue, I had already created an entry in the registry with the ATR of my particular card. I verified with certutil
that it was being loaded correctly.
I'm closing this as it's not a problem with BixVReader or the Smart Card Reader companion app! Cheers.
Expected behaviour
BixVReader handles and responds to
IOCTL_SMARTCARD_GET_FEATURE_REQUEST
messages.Actual behaviour
The message is not handled, and an error is logged, marking the message as "Not supported":
The event viewer shows:
Steps to reproduce
What I'm trying to do to solve this
Digging around, I may need to implement handling of the message in BixVReader to progress further. I found this specification document that shows the expected handling of the message, and as far as I can tell, it simply needs to be responded to. I think it might be acceptable not to populate any TLV structures as that's only required of "Class 2" drivers.
Edit: Looking at OpenSC's source here I can see that it shouldn't care if no TLV structures are provided. Just a surface-level observation, however.
Do you think that assumption is correct? I will likely come back to this in a few weeks to investigate myself if I don't hear back; setting up a test environment for driver dev on Windows seems like a pain 😉
I'm so close to having everything I need!