EvilZone
Programming and Scripting => .NET Framework => : xor June 26, 2015, 04:49:56 AM
-
/// <summary>
/// Thread-Safe Random
/// </summary>
public static class SafeRandom
{
private static readonly Random Global = new Random();
[ThreadStatic]
private static Random _local;
public static int Next()
{
var inst = _local;
if (inst != null) return inst.Next();
int seed;
lock (Global) seed = Global.Next();
_local = inst = new Random(seed);
return inst.Next();
}
}
/// <summary>
/// Thread-Safe Cryptographic Random
/// </summary>
public static class SafeCryptoRandom
{
private static readonly RNGCryptoServiceProvider Global = new RNGCryptoServiceProvider();
[ThreadStatic]
private static Random _local;
public static int Next()
{
var inst = _local;
if (inst != null) return inst.Next();
var buffer = new byte[4];
Global.GetBytes(buffer);
_local = inst = new Random(BitConverter.ToInt32(buffer, 0));
return inst.Next();
}
}
-- xor
-
Cool, but the instance members of the RNGCryptoServiceProvier are not thread safe you'll need to lock it. So something like
lock (Global) Global.GetBytes
But in general just implement it as a static class with a lazy loder. so you can simply:
static readonly ThreadLocal<Random> instance= new ThreadLocal<Random>(() => New Random(etc...)
-
Cool share, thank you!
@skruf
I'm a bit rusty on my C#, but doesn't using a static class screw up unit tests? You can't mockup a static object if I recall correctly, no?
The lock solution seems nice though, I think I remember reading an article about it a while back as well.
L.E.: Found the article (http://blogs.msdn.com/b/pfxteam/archive/2009/02/19/9434171.aspx). It's from 2009 so it might be a bit dated, but the guy suggests both the lock solution as well as using one Random instance per thread, rather than one per AppDomain (which he claims is faster).
-
Cool share, thank you!
@skruf
I'm a bit rusty on my C#, but doesn't using a static class screw up unit tests? You can't mockup a static object if I recall correctly, no?
Not that rusty :) You are absolutely correct, there are several workarounds, such as adding Reset methods or using reflection to invoke the initializer, but those are ugly and ruins the tests imho.
However, the static class is about 9x faster than the locking method, which is nice :) (Atleast when I ran them just now:P)
-
You can use something like this to make static methods testable: http://urasandesu.github.io/Prig/ (http://urasandesu.github.io/Prig/)
It's not always ideal, but actually quite good it exists for those cases that you really need it.
-
var buffer = new byte[4];
Global.GetBytes(buffer);
_local = inst = new Random(BitConverter.ToInt32(buffer, 0));
return inst.Next();
System.Random isn't cryptographically secure to my knowledge -- which is limited since I couldn't find much information about it -- and its seed space apparently is 2^32 - not outside the range of a bruteforce search and certainly faster than bruteforcing a 2^128 AES key generated using this class. You should really be using RNGCryptoServiceProvider here, or was there a technical reason you used Random instead?