RNGCryptoServiceProvider in .Net Core

后端 未结 3 1550
失恋的感觉
失恋的感觉 2020-12-09 15:12

I cannot find the System.Security.Cryptography.RNGCryptoServiceProvider class in .NetCore.

It is essential to the application I am trying to port from .Net Framework

相关标签:
3条回答
  • 2020-12-09 15:26

    We can do it like this in .Net core. It worked for me.

    RNGCryptoServiceProvider provider = new RNGCryptoServiceProvider();
    var byteArray = new byte[4];
    provider.GetBytes(byteArray);
    
    //convert 4 bytes to an integer
    var randomInteger = BitConverter.ToUInt32(byteArray, 0);
    

    It is present under the namespace : System.Security.Cryptography

    add this in your class to use the method : using System.Security.Cryptography;

    Hope it is Helpful. Thanks

    0 讨论(0)
  • 2020-12-09 15:36

    One of the solutions suggested is to use RandomNumberGenerator.Create() https://github.com/dotnet/corefx/issues/2881

    0 讨论(0)
  • 2020-12-09 15:40

    System.Security.Cryptography.RandomNumberGenerator is the base class for Cryptographically-Secure Pseudo-Random Number Generator (CSPRNG) implementations. In .NET Framework RandomNumberGenerator.Create() returns an RNGCryptoServiceProvider instance (unless configured differently by CryptoConfig). In .NET Core RandomNumberGenerator.Create() returns an opaque type which is based on BCryptGenRandom (Windows) or OpenSSL's random number generator (!Windows).

    RandomNumberGenerator.Create() is the only way to get an RNG instance on .NET Core, and since it works on both .NET Core and .NET Framework is the most portable.

    Of course, if you're generating an IV, you can also just call the instance method SymmetricAlgorithm.GenerateIV() to have it use the CSPRNG internally; though as the documentation says, calling it is unnecessary as a random IV is created with the instance (GenerateIV can be used to force it to generate a new one before the next call to CreateEncryptor).

    0 讨论(0)
提交回复
热议问题