[openssl-commits] [openssl] OpenSSL_1_0_2-stable update

[Rich Salz]

The branch OpenSSL_1_0_2-stable has been updated
       via  aaa6cd4e2d10e33a0389b3c927eb5b78f08c8b99 (commit)
      from  e1c6205c23297feb932727944ffba87be869d83a (commit)


- Log -----------------------------------------------------------------
commit aaa6cd4e2d10e33a0389b3c927eb5b78f08c8b99
Author: Benjamin Kaduk <bkaduk at akamai.com>
Date:   Thu Jun 8 15:55:30 2017 -0500

    Remove stale note from s_server.pod
    
    Modern browsers are now, well, pretty modern.
    
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/3644)
    (cherry picked from commit 36c438514db71eba3e8062fef7869b9211630a19)

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

Summary of changes:
 doc/apps/s_server.pod | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/doc/apps/s_server.pod b/doc/apps/s_server.pod
index 414efa8..767c141 100644
--- a/doc/apps/s_server.pod
+++ b/doc/apps/s_server.pod
@@ -404,10 +404,6 @@ a web browser the command:
 
 can be used for example.
 
-Most web browsers (in particular Netscape and MSIE) only support RSA cipher
-suites, so they cannot connect to servers which don't use a certificate
-carrying an RSA key or a version of OpenSSL with RSA disabled.
-
 Although specifying an empty list of CAs when requesting a client certificate
 is strictly speaking a protocol violation, some SSL clients interpret this to
 mean any CA is acceptable. This is useful for debugging purposes.