AesCryptoServiceProvider is giving slow response RRS feed

  • Question

  • When we run .net code on windows 2008 platform, we are "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms."

    To satisfy above condition, we change from "RijndaelManaged" to "AesCryptoServiceProvider". Now we are not seeing error message.

    We have logic to decrypt a data in a loop for 50000 time. Older one taking only 2 sec where are new one taking atleast 30 sec.

    Is there any way I can improve this and should satisfy FIPS.  IT's a critical for me. Pls.

    Wednesday, January 25, 2012 2:42 PM

All replies

  • To satisfy cryptographic algorithm validated by FIPS, we change logic from

    RijndaelManaged algorithm to AesCryptoServiceProvider.

    We have a condition, where it has to decrypt 50,000 entries.

    When we used RijndaelManaged algorithm, I noticed it's taking 2-3 sec. Where as AesCryptoServiceProvider giving result only after 30 sec.

    This is a performance issue and critial. Can any suggest how to improve or any suggesion any other algoritm.


    • Merged by Paul Zhou Thursday, January 26, 2012 5:04 AM the same question
    Wednesday, January 25, 2012 4:38 AM
  • Hi,

    Welcome to the MSDN forum.

    Could you please provide some code snippet to show how you implement AesCryptoServiceProvider?

    It may be caused by code logic. 


    Paul Zhou [MSFT]
    MSDN Community Support | Feedback to us
    Thursday, January 26, 2012 4:58 AM