[ Dec 13, 2017 update: The plot thickens… in early December researchers revived a 19-year-old vulnerability that allows performing RSA decryption and signing operations with the private key of a TLS server – known as The Robot Attack. ROBOT only affects TLS cipher modes that use RSA encryption.]
Aug 29, 2018 Cipher Suites | Cloudflare Developer Docs ECDHE-RSA-AES128-GCM-SHA256 Although TLS 1.3 uses the same cipher suite space as previous versions of TLS, TLS 1.3 cipher suites are defined differently, only specifying the symmetric ciphers, and cannot be used for TLS 1.2. Similarly, TLS 1.2 and lower cipher suites cannot be used with TLS 1.3 (IETF TLS 1.3 draft 21). TLS Security and Data Center Monitoring - rsa.com
TLS_ECDHE_RSA_AES_256_GCM_SHA384 Hex code: 0xC0, 0x30 TLS Version(s): TLS1.2 Protocol: Transport Layer Security (TLS) Key Exchange: Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) Authentication: Rivest Shamir Adleman algorithm (RSA) Encryption: Advanced Encryption Standard with 256bit key in Galois/Counter mode (AES 256 GCM)
RFC 5246 - The Transport Layer Security (TLS) Protocol RFC 5246 TLS August 2008 1.Introduction The primary goal of the TLS protocol is to provide privacy and data integrity between two communicating applications. The protocol is composed of two layers: the TLS Record Protocol and the TLS Handshake Protocol. At the lowest level, layered on top of some reliable transport protocol (e.g., TCP []), is the TLS Record Protocol. TLS 1.2 enabled on Web Tier but still shows TLS | RSA Link
Aug 30, 2017
In practice, some third-party TLS clients do not comply with the TLS 1.2 RFC and fail to include all the signature and hash algorithm pairs they are willing to accept in the "signature_algorithms" extension, or omit the extension altogether (the latter indicates to the server that the client only supports SHA1 with RSA, DSA or ECDSA). A TLS server often only has one certificate configured per endpoint, which …