Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bigints: update cryptography usage. #20272

Merged
merged 2 commits into from
Sep 3, 2022
+1 −1
Merged

Bigints: update cryptography usage. #20272

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
269db5b
Bigints: update cryptography usage.
paulmillr Sep 3, 2022
132cbec
Update files/en-us/web/javascript/reference/global_objects/bigint/ind…
Josh-Cena Sep 3, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion files/en-us/web/javascript/reference/global_objects/bigint/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,7 +229,7 @@ Because coercing between Number values and BigInt values can lead to loss of pre

### Cryptography

The operations supported on BigInt values are not constant-time, and are thus open to [timing attacks](https://en.wikipedia.org/wiki/Timing_attack). JavaScript BigInts are therefore not well-suited for use in cryptography.
The operations supported on BigInt values are not constant-time, and are thus open to [timing attacks](https://en.wikipedia.org/wiki/Timing_attack). JavaScript BigInts are therefore could be dangerous for use in cryptography without mitigating factors. As a very generic example, attacker could measure time difference between 101n ** 65537n and 17n ** 9999n, and deduce secrets, such as private keys, based on the time passed. If you still have to use bigints, take a look at https://timing.attacks.cr.yp.to/programming.html for general advice regarding the issue.

### Use within JSON

Expand Down