[openssl-commits] [openssl] OpenSSL_1_1_0-stable update

[Rich Salz]

The branch OpenSSL_1_1_0-stable has been updated
       via  a0cdcf9bc8619df97699e4cc34994366d4306c3e (commit)
      from  fd2975883d51c475247d3d8a5919b380944b9a46 (commit)


- Log -----------------------------------------------------------------
commit a0cdcf9bc8619df97699e4cc34994366d4306c3e
Author: FdaSilvaYY <fdasilvayy at gmail.com>
Date:   Fri Feb 10 23:17:00 2017 +0100

    Spelling fixes
    
    Reviewed-by: Andy Polyakov <appro at openssl.org>
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/3066)
    (cherry picked from commit a8cd439bf58708ffe234a9f707cf6a394d28a1f9)

-----------------------------------------------------------------------

Summary of changes:
 CHANGES | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CHANGES b/CHANGES
index 6446b9c..bfa5605 100644
--- a/CHANGES
+++ b/CHANGES
@@ -186,7 +186,7 @@
      to service a connection. This could lead to a Denial of Service through
      memory exhaustion. However, the excessive message length check still takes
      place, and this would cause the connection to immediately fail. Assuming
-     that the application calls SSL_free() on the failed conneciton in a timely
+     that the application calls SSL_free() on the failed connection in a timely
      manner then the 21Mb of allocated memory will then be immediately freed
      again. Therefore the excessive memory allocation will be transitory in
      nature. This then means that there is only a security impact if:
@@ -939,7 +939,7 @@
      done while fixing the error code for the key-too-small case.
      [Annie Yousar <a.yousar at informatik.hu-berlin.de>]
 
-  *) CA.sh has been removmed; use CA.pl instead.
+  *) CA.sh has been removed; use CA.pl instead.
      [Rich Salz]
 
   *) Removed old DES API.