summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRob Janssen <rob@devcorner.nl>2015-03-17 12:21:25 +0100
committerRob Janssen <rob@devcorner.nl>2015-03-17 12:21:25 +0100
commite27b1e0ed974ed8cb3dd08afeca4c46b193c67cb (patch)
treec1a9ad844e7a21f2fa379c12d2db937374c22fa2
parent496350c9382556d6481686d230f71a1d55817808 (diff)
downloadTwoFactorAuth-e27b1e0ed974ed8cb3dd08afeca4c46b193c67cb.zip
TwoFactorAuth-e27b1e0ed974ed8cb3dd08afeca4c46b193c67cb.tar.gz
TwoFactorAuth-e27b1e0ed974ed8cb3dd08afeca4c46b193c67cb.tar.bz2
Update README.md
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 802ea55..1c1b7c9 100644
--- a/README.md
+++ b/README.md
@@ -149,7 +149,7 @@ VoilĂ . Couldn't make it any simpler.
### RNG providers
-This class also comes with three 'built-in' RNG providers (Random Number Generator). The RNG provider generates a number of random bytes and returns these bytes as an array. These values are then used to create the secret. By default (no RNG provider specified) TwoFactorAuth will try to determine the best available RNG provider to use. It will, be default, try to use the `MCryptRNGProvider`, if this is not available/supported for any reason it will try to use the `OpenSSLRNGProvider` and if that is also not available/supported it will try to use the final RNG provider: `HashRNGProvider`. Each of these providers use their own method of generating a random sequence of bytes. The first two (`OpenSSLRNGProvider` and `MCryptRNGProvider`) return a cryptographically secure sequence of random bytes whereas the `HashRNGProvider` returns a **non-cryptographically secure** sequence.
+This class also comes with three 'built-in' RNG providers (Random Number Generator). The RNG provider generates a number of random bytes and returns these bytes as a string. These values are then used to create the secret. By default (no RNG provider specified) TwoFactorAuth will try to determine the best available RNG provider to use. It will, be default, try to use the `MCryptRNGProvider`, if this is not available/supported for any reason it will try to use the `OpenSSLRNGProvider` and if that is also not available/supported it will try to use the final RNG provider: `HashRNGProvider`. Each of these providers use their own method of generating a random sequence of bytes. The first two (`OpenSSLRNGProvider` and `MCryptRNGProvider`) return a cryptographically secure sequence of random bytes whereas the `HashRNGProvider` returns a **non-cryptographically secure** sequence.
You can easily implement your own `RNDProvider` by simply implementing the `IRNGProvider` interface. Each of the 'built-in' RNG providers have some constructor parameters that allow you to 'tweak' some of the settings to use when creating the random bytes such as which source to use (`MCryptRNGProvider`) or which hashing algorithm (`HashRNGProvider`).