summaryrefslogtreecommitdiffstats
path: root/CHANGES.md
diff options
context:
space:
mode:
authorDimitri Papadopoulos <3234522+DimitriPapadopoulos@users.noreply.github.com>2024-06-20 20:42:46 +0200
committerTomas Mraz <tomas@openssl.org>2024-06-24 15:09:11 +0200
commit8f250985ad1ac4efc25621ce2504c52ef0cbe283 (patch)
treeb419c25d7e1ee85db0de71175177654d7a8059fb /CHANGES.md
parentExtend `mask` of `ssl_method_st` to 64-bit (diff)
downloadopenssl-8f250985ad1ac4efc25621ce2504c52ef0cbe283.tar.xz
openssl-8f250985ad1ac4efc25621ce2504c52ef0cbe283.zip
Fix typos found by codespell
Reviewed-by: Paul Dale <ppzgs1@gmail.com> Reviewed-by: Kurt Roeckx <kurt@roeckx.be> (Merged from https://github.com/openssl/openssl/pull/24691)
Diffstat (limited to 'CHANGES.md')
-rw-r--r--CHANGES.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/CHANGES.md b/CHANGES.md
index 9eed55ab76..0f3701c6d5 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -318,7 +318,7 @@ OpenSSL 3.3
*Fisher Yu*
- * Enable AES and SHA3 optimisations on Applie Silicon M3-based MacOS systems
+ * Enable AES and SHA3 optimisations on Apple Silicon M3-based MacOS systems
similar to M1/M2.
*Tom Cosgrove*
@@ -3092,7 +3092,7 @@ breaking changes, and mappings for the large list of deprecated functions.
this switch breaks interoperability with correct implementations.
* Fix a use after free bug in d2i_X509_PUBKEY when overwriting a
- re-used X509_PUBKEY object if the second PUBKEY is malformed.
+ reused X509_PUBKEY object if the second PUBKEY is malformed.
*Bernd Edlinger*
@@ -4426,7 +4426,7 @@ OpenSSL 1.1.0
*Billy Bob Brumley, Nicola Tuveri*
* Fix a use after free bug in d2i_X509_PUBKEY when overwriting a
- re-used X509_PUBKEY object if the second PUBKEY is malformed.
+ reused X509_PUBKEY object if the second PUBKEY is malformed.
*Bernd Edlinger*
@@ -16546,7 +16546,7 @@ s-cbc 3624.96k 5258.21k 5530.91k 5624.30k 5628.26k
*Bodo Moeller*
* Store verify_result within SSL_SESSION also for client side to
- avoid potential security hole. (Re-used sessions on the client side
+ avoid potential security hole. (Reused sessions on the client side
always resulted in verify_result==X509_V_OK, not using the original
result of the server certificate verification.)