Konstantin Romanov has also posted a winscard implementation: https://gitlab.winehq.org/wine/wine/-/merge_requests/2249
The server side implementation in libpcslite should be moved to scardmgr service (scardmgr.dll) and the client implementation should eventually use it. Any plans on the above (probably my understanding is wrong, please check).
It provides roughly the same function but I'm not convinced it needs to be moved there. Applications don't interact directly with scardsvr AFACT.
According to MS (https://learn.microsoft.com/en-us/windows/win32/secauthn/smart-card-resource...), all the resource requests and handling for smartcards handled by resource manager (scardsvr.dll). For now basic implementation is good enough to make it work.
Yes, I think we could just have a stub. Also note that if you move the server to Wine you would need to resolve the conflict with a native server managing the same hardware.
On Tue Feb 21 16:33:04 2023 +0000, Vijay Kiran Kamuju wrote:
According to MS (https://learn.microsoft.com/en-us/windows/win32/secauthn/smart-card-resource...), all the resource requests and handling for smartcards handled by resource manager (scardsvr.dll). For now basic implementation is good enough to make it work.
In this case, the resource manager is pcscd. This code does not implement the functionality of the manager itself. It just calls its functions through libpcsclite1.
-
Hans Leidekker (＠hans) -
Konstantin Romanov (＠IncubusRK)
-
Vijay Kiran Kamuju (＠infyquest)