From 141b65fea85c3d03ea3e60affeb3d6955c6229cf Mon Sep 17 00:00:00 2001 From: Ahmed Farid Date: Mon, 29 Aug 2022 18:18:19 +0100 Subject: [PATCH] Fix typo --- .../TimingAttackAgainstHash/TimingAttackAgainstHash.qhelp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/python/ql/src/experimental/Security/CWE-208/TimingAttackAgainstHash/TimingAttackAgainstHash.qhelp b/python/ql/src/experimental/Security/CWE-208/TimingAttackAgainstHash/TimingAttackAgainstHash.qhelp index 5f1b1feb8e3..2dfe5296167 100644 --- a/python/ql/src/experimental/Security/CWE-208/TimingAttackAgainstHash/TimingAttackAgainstHash.qhelp +++ b/python/ql/src/experimental/Security/CWE-208/TimingAttackAgainstHash/TimingAttackAgainstHash.qhelp @@ -6,7 +6,7 @@ Timing Attack is based on the leakage of information by studying how long it takes the system to respond to different inputs. it can be circumvented by using a constant-time algorithm for checking the value of Hash, more precisely, the comparison time should not depend on the content of the input. Otherwise the attacker gains -information that is indirectly leaked by the application. This information is then used for malicious purposes. +information that is indirectly leaked by the application. This information may then be used for malicious purposes.