Commit 1bf6250
doc : mention constant-time in crypto doc
Included reference to 'constant time' in
crypto.timingSafeEqual description.
The Node website would score higher on a Google search
and the API would be more discoverable if it used the words
"constant time" in its description.
PR-URL: #16604
Fixes: #16504
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent 542f3b9 commit 1bf6250
1 file changed
Lines changed: 1 addition & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1848,6 +1848,7 @@ added: v6.6.0 | |||
| 1848 | 1848 | - `a` {Buffer | TypedArray | DataView} | |
| 1849 | 1849 | - `b` {Buffer | TypedArray | DataView} | |
| 1850 | 1850 | ||
| 1851 | + This function is based on a constant-time algorithm. | ||
| 1851 | 1852 | Returns true if `a` is equal to `b`, without leaking timing information that | |
| 1852 | 1853 | would allow an attacker to guess one of the values. This is suitable for | |
| 1853 | 1854 | comparing HMAC digests or secret values like authentication cookies or | |
0 commit comments