none
What is the replacement for custom CSP since CryptoAPI is being deprecated as announced ? RRS feed

  • Question

  • Hello,

    I'm wondering what is the replacement for custom CSP since all CryptoAPI functions are marked deprecated in the MSDN pages.

    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 ?

    Thanks in advance.

    Wednesday, February 28, 2018 1:18 PM

All replies

  • 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

    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

    But both older technologies still work.

    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.

    • Proposed as answer by Adam Gross Monday, March 19, 2018 2:54 PM
    Friday, March 9, 2018 5:24 PM