Skip to content

Commit c2c4d9e

Browse files
` change to <code>
Co-authored-by: intrigus-lgtm <[email protected]>
1 parent d7314a1 commit c2c4d9e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

ruby/ql/src/experimental/insecure-randomness/InsecureRandomness.qhelp

+5-5
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ perform actions that would otherwise be beyond their reach. For instance, if an
2424
predict a newly generated user's random password, they would gain unauthorized access to that user's
2525
account.
2626

27-
For Ruby, `SecureRandom` provides a cryptographically secure pseudo-random number generator.
28-
`rand` is not cryptographically secure, and should be avoided in security contexts.
29-
For contexts which are not security sensitive, Random may be preferable as it has a more convenient
27+
For Ruby, <code>SecureRandom</code> provides a cryptographically secure pseudo-random number generator.
28+
<code>rand</code> is not cryptographically secure, and should be avoided in security contexts.
29+
For contexts which are not security sensitive, <code>Random</code> may be preferable as it has a more convenient
3030
interface.
3131

3232
</p>
@@ -37,11 +37,11 @@ interface.
3737
The following examples show different ways of generating a password.
3838
</p>
3939

40-
<p>The first example uses `Random.rand()` which is not for security purposes</p>
40+
<p>The first example uses <code>Random.rand()</code> which is not for security purposes</p>
4141

4242
<sample src="examples/InsecureRandomnessBad.rb" />
4343

44-
<p>In the second example, the password is generated using `SecureRandom.random_bytes` which is a
44+
<p>In the second example, the password is generated using <code>SecureRandom.random_bytes()</code> which is a
4545
cryptographically secure method.</p>
4646

4747
<sample src="examples/InsecureRandomnessGood.rb" />

0 commit comments

Comments
 (0)