diff options
author | Jack Lloyd <[email protected]> | 2018-09-28 10:48:41 -0400 |
---|---|---|
committer | Jack Lloyd <[email protected]> | 2018-09-28 10:51:12 -0400 |
commit | 8e6fa0a74ee5bf3fcf129ae1c474a3d732500f74 (patch) | |
tree | db9d7f035bdcea3ee1e36dcc5ad1dd4afa825a58 /doc/manual/secmem.rst | |
parent | 519b21c9586045be3e9316e57bbc5c68ba5841da (diff) |
Spell check the documentation
Diffstat (limited to 'doc/manual/secmem.rst')
-rw-r--r-- | doc/manual/secmem.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/manual/secmem.rst b/doc/manual/secmem.rst index ce5ff205b..8dd479b7e 100644 --- a/doc/manual/secmem.rst +++ b/doc/manual/secmem.rst @@ -2,10 +2,10 @@ Memory container ======================================== -A major concern with mixing modern multiuser OSes and cryptographic +A major concern with mixing modern multi-user OSes and cryptographic code is that at any time the code (including secret keys) could be swapped to disk, where it can later be read by an attacker, or left -floating around in memory for later retreval. +floating around in memory for later retrieval. For this reason the library uses a ``std::vector`` with a custom allocator that will zero memory before deallocation, named via typedef @@ -15,7 +15,7 @@ love. Some operating systems offer the ability to lock memory into RAM, preventing swapping from occurring. Typically this operation is -restricted to privledged users (root or admin), however some OSes +restricted to privileged users (root or admin), however some OSes including Linux and FreeBSD allow normal users to lock a small amount of memory. On these systems, allocations first attempt to allocate out of this small locked pool, and then if that fails will fall back to |