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

Fixing typo in Security section #2522

Closed
wants to merge 2 commits into from
Closed

Fixing typo in Security section #2522

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9eefea5
Fixing typo in Side-Channel Attacks section
PhoeniXAbhisheK Jan 10, 2022
553aec3
More typo fixes to Security section
PhoeniXAbhisheK Jan 10, 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
8 changes: 4 additions & 4 deletions docs.wrm/concepts/security/index.wrm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ importantly securely released.

[Historically](https://github.com/nodejs/node/issues/4660),
``new Buffer(16)`` would re-use old memory that had been
released. This would mean that code runnint later, may have
released. This would mean that code running later, may have
access to data that was discarded.

As an example of the dangers, imagine if you had used a Buffer
Expand All @@ -37,9 +37,9 @@ have that left-over private key, which it could then use to
steal the funds from that account.

There are also many debugging tools and systems designed to
assist develoeprs inspect the memory contents of JavaScript
assist developers inspect the memory contents of JavaScript
programs. In these cases, any //private key// or //mnemonic//
siiting in memory may be visible to other users on the system,
sitting in memory may be visible to other users on the system,
or malicious scripts.

_heading: Timing Attack
Expand All @@ -65,7 +65,7 @@ will. By timing how long the code took to execute, they now know
whether garbage collection occured and therefore whether the simple
or complex path was taken.

Advancced timing attacks are very difficult to mitigate in any
Advanced timing attacks are very difficult to mitigate in any
garbage-collection-based language. Most libraries where this
matters will hopefully mitigated this for you as much as possible,
but it is still good to be aware of.
Expand Down