summaryrefslogtreecommitdiff
path: root/lisp/net/nsm.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2019-12-09 18:44:35 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2019-12-09 18:45:18 -0800
commitd1a791f8edc1b8f2189b6f1b3be7b946fef1edbc (patch)
treefb415df3de5b00b9ce7616872ead40c983b55a12 /lisp/net/nsm.el
parent28578f87b52ead4d31479fdcfba028118dfa6987 (diff)
downloademacs-d1a791f8edc1b8f2189b6f1b3be7b946fef1edbc.tar.gz
Spelling fixes
Diffstat (limited to 'lisp/net/nsm.el')
-rw-r--r--lisp/net/nsm.el6
1 files changed, 3 insertions, 3 deletions
diff --git a/lisp/net/nsm.el b/lisp/net/nsm.el
index 5dc5244e6d5..e430daa3823 100644
--- a/lisp/net/nsm.el
+++ b/lisp/net/nsm.el
@@ -384,7 +384,7 @@ Security (DTLS)\", \"(4.1. General Guidelines)\"
This check is a response to Logjam[1]. Logjam is an attack that
allows an attacker with sufficient resource, and positioned
between the user and the server, to downgrade vulnerable TLS
-connections to insecure 512-bit export grade crypotography.
+connections to insecure 512-bit export grade cryptography.
The Logjam paper suggests using 1024-bit prime on the client to
mitigate some effects of this attack, and upgrade to 2048-bit as
@@ -550,7 +550,7 @@ Security (TLS) and Datagram Transport Layer Security (DTLS)\",
Due to its use of 64-bit block size, it is known that a
ciphertext collision is highly likely when 2^32 blocks are
encrypted with the same key bundle under 3-key 3DES. Practical
-birthday attacks of this kind have been demostrated by Sweet32[1].
+birthday attacks of this kind have been demonstrated by Sweet32[1].
As such, NIST is in the process of disallowing its use in TLS[2].
[1]: Bhargavan, Leurent (2016). \"On the Practical (In-)Security of
@@ -752,7 +752,7 @@ protocol."
;; Plain connection allowed.
(memq :none saved-fingerprints)
;; We are pinning certs, and we have seen this host before,
- ;; but the credientials for this host differs from the last
+ ;; but the credentials for this host differs from the last
;; times we saw it.
(member (nsm-fingerprint status) saved-fingerprints))))