summaryrefslogtreecommitdiff
path: root/sites
diff options
context:
space:
mode:
authorJeff Forcier <jeff@bitprophet.org>2023-01-27 17:18:06 -0500
committerJeff Forcier <jeff@bitprophet.org>2023-01-27 17:18:06 -0500
commit19e5db81ec13ef3aeeb8c12f94d096376d8d8f4c (patch)
treeb13efe3abe3b918c4b566bc8a53b8497d3c4bc62 /sites
parent04b12990e5e41739f35b58971e21890d201c5503 (diff)
downloadparamiko-19e5db81ec13ef3aeeb8c12f94d096376d8d8f4c.tar.gz
Tidy up codespellrc, revert s/keypair/key pair/
Diffstat (limited to 'sites')
-rw-r--r--sites/www/changelog.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst
index ae1d7365..239c9e2c 100644
--- a/sites/www/changelog.rst
+++ b/sites/www/changelog.rst
@@ -334,7 +334,7 @@ Changelog
This fixes a security flaw! If you are running Paramiko on 32-bit systems
with low entropy (such as any 32-bit Python 2, or a 32-bit Python 3 which
is running with ``PYTHONHASHSEED=0``) it is possible for an attacker to
- craft a new key pair from an exfiltrated public key, which Paramiko would
+ craft a new keypair from an exfiltrated public key, which Paramiko would
consider equal to the original key.
This could enable attacks such as, but not limited to, the following: