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

[Richard Levitte]

The branch OpenSSL_1_1_0-stable has been updated
       via  fae00c9321e9d843355b37358a12756634e267e6 (commit)
      from  64b5b5bd7cfdef1f1204fa305e9d685de8bf5b7f (commit)


- Log -----------------------------------------------------------------
commit fae00c9321e9d843355b37358a12756634e267e6
Author: Richard Levitte <levitte at openssl.org>
Date:   Fri Dec 8 11:40:30 2017 +0100

    Remove unicode characters from source
    
    Some compilers react badly to non-ASCII characters
    
    Fixes #4877
    
    Reviewed-by: Matt Caswell <matt at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/4879)
    
    (cherry picked from commit d68a0eaf45f12392065f3cf716a1a2682d55d3ce)

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

Summary of changes:
 test/bad_dtls_test.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/bad_dtls_test.c b/test/bad_dtls_test.c
index 1408a13..2e33010 100644
--- a/test/bad_dtls_test.c
+++ b/test/bad_dtls_test.c
@@ -19,7 +19,7 @@
  * Note that unlike other SSL tests, we don't test against our own SSL
  * server method. Firstly because we don't have one; we *only* support
  * DTLS1_BAD_VER as a client. And secondly because even if that were
- * fixed up it's the wrong thing to test against — because if changes
+ * fixed up it's the wrong thing to test against - because if changes
  * are made in generic DTLS code which don't take DTLS1_BAD_VER into
  * account, there's plenty of scope for making those changes such that
  * they break *both* the client and the server in the same way.