问题描述
您好，
我想知道自定义CSP的替代品是什么，因为所有CryptoAPI函数都在MSDN页面中被标记为已弃用。
I'm wondering what is the replacement for custom CSP since all CryptoAPI functions are marked deprecated in the MSDN pages.
我们为法国智能卡维护了这样一个CSP中间件，我们担心这一点。
We have such a CSP middleware under maintenance for french smartcard and we are worrying about that.
有什么办法可以管理第三方智能卡？
What are the alternatives to manage the third party smartcard ?
提前致谢。
推荐答案
1）Microsoft建议新的智能卡CSP实现使用min驱动程序架构，因为它会为您处理读者交互。
1) Microsoft recommends that new smart card CSP implementations use the min driver architecture, since it handles the reader interaction for you.
https://docs.microsoft.com/en-us/windows-hardware/drivers/smartcard/smart-card-minidrivers
https://docs.microsoft.com/en-us/windows-hardware/drivers/smartcard/smart-card-minidrivers
2）Microsoft建议应用程序编写者使用CryptoAPI Next生成而不是CryptoAPI。
2) Microsoft recommends that application writers use the CryptoAPI Next Generation instead of CryptoAPI.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa376210(v = vs.85）.aspx
https://msdn.microsoft.com/en-us/library/windows/desktop/aa376210(v=vs.85).aspx
但两种旧技术仍然有效。
But both older technologies still work.
我不会在Microsoft发布CSP无法运行的操作系统之前，请担心您的CSP实施。 在广泛的操作系统部署期间，您将有时间适应新的情况。
I would not worry about your CSP implementation until Microsoft ships an OS for which the CSP does not work. During the time it takes for widespread OS deployment, you will have time to adapt to the new situation.
这篇关于自从CryptoAPI被宣布弃用后，自定义CSP的替代品是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！