summaryrefslogtreecommitdiff
path: root/Readme.txt
diff options
context:
space:
mode:
authorThe Potato Chronicler <45178972+ThePotatoChronicler@users.noreply.github.com>2021-07-14 23:59:04 +0000
committerGitHub <noreply@github.com>2021-07-14 19:59:04 -0400
commitbc7d1bafa1e8ac732396374f0bca94ab9f396f1c (patch)
tree0dd296bd08b2fe66cbe0aae94a670b7e5a08a0e4 /Readme.txt
parentdf06a2d4dfc01eff6454b4e2aac899890a3dc3b5 (diff)
downloadcryptopp-git-bc7d1bafa1e8ac732396374f0bca94ab9f396f1c.tar.gz
Fix typos (PR #1061)
Diffstat (limited to 'Readme.txt')
-rw-r--r--Readme.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Readme.txt b/Readme.txt
index e74d5666..208a1e87 100644
--- a/Readme.txt
+++ b/Readme.txt
@@ -212,14 +212,14 @@ to internal buffer attacks as "Microarchitectural Data Sampling" (MDS).
The library uses hardware instructions when possible for block ciphers, hashes
and other operations. The hardware acceleration remediates some timing
-attacks. The library also uses cache-aware algoirthms and access patterns
+attacks. The library also uses cache-aware algorithms and access patterns
to minimize leakage cache evictions.
Elliptic curves over binary fields are believed to leak information. The task is a
work in progress. We don't believe binary fields are used in production, so we feel it
is a low risk at the moment.
-Crypto++ does not enagage Specter remediations at this time. The GCC options
+Crypto++ does not engage Specter remediations at this time. The GCC options
for Specter are -mfunction-return=thunk and -mindirect-branch=thunk, and the
library uses them during testing. If you want the Specter workarounds then add
the GCC options to your CXXFLAGS when building the library.