diff --git a/csharp/ql/src/Security Features/InsecureRandomness.qhelp b/csharp/ql/src/Security Features/InsecureRandomness.qhelp index b0fe5a5513ee..6f9634643ec3 100644 --- a/csharp/ql/src/Security Features/InsecureRandomness.qhelp +++ b/csharp/ql/src/Security Features/InsecureRandomness.qhelp @@ -29,11 +29,6 @@ number generator. Random is not cryptographically secure, and shoul security contexts. For contexts which are not security sensitive, Random may be preferable as it has a more convenient interface, and is likely to be faster.

-

-For the specific use-case of generating passwords, consider -System.Web.Security.Membership.GeneratePassword, which provides a cryptographically -secure method of generating random passwords. -

@@ -54,10 +49,7 @@ purpose. In this case, it is much harder to predict the generated integers.

In the final example, the password is generated using the Membership.GeneratePassword -library method, which uses a cryptographically secure random number generator to generate a random -series of characters. This method should be preferred when generating passwords, if possible, as it -avoids potential pitfalls when converting the output of a random number generator (usually an int or -a byte) to a series of permitted characters. +library method, which generates a password with a bias, therefore should be avoided.