關於 tls_aes_256_gcm_sha384 ，我們在網路上蒐集到這些相關的討論、資訊與評價

#11. TLS_AES_256_GCM_SHA384 - Apple Developer

Global Variable. TLS_AES_256_GCM_SHA384. No overview available. Availability. iOS 11.0+; macOS 10.13+; Mac Catalyst 13.0+; tvOS 11.0+; watchOS 4.0+.

#12. 6.3.2 Encrypted Connection TLS Protocols and Ciphers

TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_CCM_SHA256 TLS_AES_128_CCM_8_SHA256.

#13. TLS Forward Secrecy in Postfix

Received: from localhost (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ...

#14. 阿群的笔记(同步备份自简书)-程序员资料

TLS 1.3套件TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256_阿群的笔记(同步备份自简书)-程序员资料. TLS 1.3套件.

#15. How do I disable just one cipher out of OpenSSL TLSv1.3 list?

A TLS-compliant application MUST implement the TLS_AES_128_GCM_SHA256 [GCM] cipher suite and SHOULD implement the TLS_AES_256_GCM_SHA384 ...

#16. Decrypt SSL traffic with certificates and private keys

0x1302, TLS_AES_256_GCM_SHA384, TLS_AES_256_GCM_SHA384, Yes. 0x1303, TLS_CHACHA20_POLY1305_SHA256, TLS_CHACHA20_POLY1305_SHA256, Yes.

#17. Projects / SSL Client Test - Qualys SSL Labs

TLS_AES_256_GCM_SHA384 ( 0x1302 ) Forward Secrecy, 256. TLS_CHACHA20_POLY1305_SHA256 ( 0x1303 ) Forward Secrecy, 256.

#18. rfc8446 - IETF Tools

... [GCM] cipher suite and SHOULD implement the TLS_AES_256_GCM_SHA384 [GCM] and TLS_CHACHA20_POLY1305_SHA256 [RFC8439] cipher suites (see Appendix B.4).

#19. Configuring a Cipher Suites List Using TLS v1.3 - Micro Focus

TLS1.3 Cipher Suites. The following are the new collections of cipher suites used in TLS v1.3: TLS_AES_256_GCM_SHA384 (Enabled by default) ...

#20. D.2. Available algorithms - Cendio

Here are all the available algorithms for use in a priority string in ThinLinc. D.2.1. Cipher suites. TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 ...

#21. TLS 1.3套件TLS_CHACHA20_POLY1305_SHA256 ... - 简书

TLS 1.3套件0x13,0x02 - TLS_AES_256_GCM_SHA384 0x13,0x03 - TLS_CHACHA20_POLY1305_SHA256 0...

#22. 管理TLS安全性原則

阿聯酋（杜拜）. 僅支援前向安全的加密套件，安全性極高, TLS1.2及TLS1.3, TLS_AES_128_GCM_SHA256、TLS_AES_256_GCM_SHA384、 ...

#23. TLS_AES_256_GCM_SHA384 - OkHttp

TLS_AES_256_GCM_SHA384 ¶. val TLS_AES_256_GCM_SHA384: CipherSuite. Copyright © 2019 Square, Inc. Made with Material for MkDocs.

#24. #1118 (OpenVPN 2.4.6 does not respect -tls-cipher priority ...

Thus it seems impossible to use the ChaCha20-Poly1305 Cipher on the TLS Control Channel when using tls 1.3, as TLS_AES_256_GCM_SHA384 is always given priority.

#25. Java Secure Socket Extension (JSSE) Reference Guide

java:291|Ignore unsupported cipher suite: TLS_AES_256_GCM_SHA384 for TLS12 javax.net.ssl|DEBUG|01|main|2018-08-18 01:04:47.577 EDT|HandshakeContext.java:291| ...

#26. 阿群的笔记(同步备份自简书)-程序员宅基地

TLS 1.3套件TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256_阿群的笔记(同步备份自简书)-程序员宅基地. TLS 1.3套件.

#27. Testing TLSv1.3 and supported ciphers - SANS Internet Storm ...

New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Server public key is 256 bit. Secure Renegotiation IS NOT supported. Compression: NONE

#28. New test/javax/net/ssl/TLS/TestJSSEClientDefaultProtocol.java

... -Djdk.tls.client.protocols=TLSv1.3 57 * -DCIPHER=TLS_AES_256_GCM_SHA384 58 * TestJSSE 59 * @run main/othervm 60 * -DSERVER_PROTOCOL=SSLv2Hello,SSLv3 ...

#29. 阿群的笔记(同步备份自简书)-CSDN博客

TLS 1.3套件TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256. liuqun69 2019-06-24 12:52:00 2731 收藏.

#30. The following sslciphersuite settings are invalid and were ...

Symptoms You see an error when adding an SSL cipher suite such as TLS_AES_256_GCM_SHA384 to Apache. When trying to save your changes in...

#31. Supported protocols and ciphers between viewers and ...

TLS_AES_256_GCM_SHA384, TLS_AES_256_GCM_SHA384. TLS_CHACHA20_POLY1305_SHA256, TLS_CHACHA20_POLY1305_SHA256. Supported ECDSA ciphers.

#32. 一起幫忙解決難題，拯救IT 人的一天

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 - TLS_AES_128_GCM_SHA256 - TLS_AES_256_GCM_SHA384 - TLS_AES_128_CCM_SHA256.

#33. SGOS and TLS 1.3 only client apps | ProxySG & Advanced ...

TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 Since the existing tls 1.3 support in SGOS is to downgrade the ...

#34. tls package - crypto/tls - pkg.dev - Golang

TLS_AES_128_GCM_SHA256 uint16 = 0x1301 TLS_AES_256_GCM_SHA384 uint16 = 0x1302 TLS_CHACHA20_POLY1305_SHA256 uint16 = 0x1303 // TLS_FALLBACK_SCSV isn't a ...

#35. src/crypto/tls/cipher_suites.go - go - Git at Google

{TLS_AES_256_GCM_SHA384, 32, aeadAESGCMTLS13, crypto.SHA384},. } // cipherSuitesPreferenceOrder is the order in which we'll select (on the.

#36. Why doesn't Windows send all enabled cipher suites during ...

You start out with this custom list of suites: TLS_AES_256_GCM_SHA384 TLS_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 ...

#37. Issues connecting to *.sophosupd.com "Server did not ...

03.07.2021 09:26 Error 184.30.25.172 d1.sophosupd.com TLS_AES_256_GCM_SHA384 Server did not respond to client hello.

#38. Characterization of cipher suite selection, downgrading, and ...

However, many of the weak ciphers were also present here. The fourth cipher suite in TLS 1.3, TLS_AES_256_GCM_SHA384, 384 bit ECDH (P-384), was used less than ...

#39. 1432907 – Cipher suite mismatch with latest nss - Red Hat ...

GCM capture.txt TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 Additional info: The latest nss-3.28.3-3.el7 supports these suites: ...

#40. 阿群的笔记(同步备份自简书)-程序员秘密

TLS 1.3套件TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256_阿群的笔记(同步备份自简书)-程序员秘密. TLS 1.3套件.

#41. TLS All The Things! Perfect 100 SSL-Labs Score Revisited

angelique@dawnbringer:/usr/local/src$ openssl ciphers -s -v | grep 1.3 TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD ...

#42. SSL/TLS versions and cipher suites - Handbook | FortiADC ...

Profiles support TLS_AES_128_GCM_SHA256 and TLS_AES_256_GCM_SHA384 for TLSv1.3. They will be set automatically when TLSv1.3 is selected in ssl version. You ...

#43. TLS Cipher String - OWASP Cheat Sheet Series

The Mozilla Foundation provides an easy-to-use secure configuration generator for web, database, and mail software. This online (and well updated) tools allows ...

#44. TLSv1.3 and ECDSA not tested? - Qualys, Inc.

... TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Server public key is 384 bit ... a TLSv1.3 connection TLS_AES_256_GCM_SHA384 using the ECDSA cert.

#45. 阿群的笔记(同步备份自简书)-程序员信息网

TLS 1.3套件TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256_阿群的笔记(同步备份自简书)-程序员信息网. TLS 1.3套件.

#46. RSA 4096 bits (SHA256withRSA) Certificate #2 - netfiles.de

TLS_AES_256_GCM_SHA384 ECDH x25519 FS. BingPreview Jan 2015. RSA 4096 (SHA256). TLS 1.2. TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS.

#47. Configuring TLS 1.3 on WildFly application Server

openssl ciphers -tls1_3 -v -s TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 ...

#48. Supported ciphersuites (GnuTLS 3.7.2)

Ciphersuite name TLS ID Since TLS_AES_128_GCM_SHA256 0x13 0x01 TLS1.3 TLS_AES_256_GCM_SHA384 0x13 0x02 TLS1.3 TLS_CHACHA20_POLY1305_SHA256 0x13 0x03 TLS1.3

#49. CipherSuite (OkHttp 3.12.1 API) - mvndoc.com

static CipherSuite · TLS_AES_256_GCM_SHA384. static CipherSuite · TLS_CHACHA20_POLY1305_SHA256. static CipherSuite · TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA.

#50. TLS Handshake exception #53 - githubmemory

... (native) No connection Android 9.0 (native) TLSv1.3 TLS_AES_256_GCM_SHA384 253 bit ECDH (X25519) Android 10.0 (native) TLSv1.3 TLS_AES_256_GCM_SHA384 ...

#51. Restrict TLS protocols and cipher suites—ArcGIS Server

TLS_AES_256_GCM_SHA384 (TLSv1.3 only); TLS_AES_128_GCM_SHA256 (TLSv1.3 only). For security reasons, several encryption algorithms that were enabled by ...

#52. TLS_AES_256_GCM_SHA384, not reused, no cert - Let's ...

"SSL version: TLSv1.3, SSL cipher: TLS_AES_256_GCM_SHA384, not reused, no cert" ! This is the configuration of my certification in vsftpd.

#53. Cipher support on a Citrix MPX/SDX (N3) appliance

TLS_AES_256_GCM_SHA384 12.1-50.x,. 13.0. NA. TLS1.3-CHACHA20-. POLY1305-SHA256. 0x1303. TLS_CHACHA20_POLY1305_S. HA256. 12.1-50.x,.

#54. Customise TLS 1.3 cipher suites - Help - Caddy Community

... thus listed by strength) x1302 TLS_AES_256_GCM_SHA384 ECDH 253 AESGCM 256 TLS_AES_256_GCM_SHA384 x1303 TLS_CHACHA20_POLY1305_SHA256 ECDH ...

#55. TLSv1.3: Minor Version, Major Changes - F5

would be TLS_AES_256_GCM_SHA384. • TLSv1.2 and earlier cipher suites do not work in TLSv1.3. • Note all TLSv1.3 cipher suites begin with “TLS13” on BIG-IP.

#56. Cipher (Apache Tomcat 8.5.73 API Documentation)

TLS_AES_256_GCM_SHA384 · TLS_CHACHA20_POLY1305_SHA256 ... TLS_AES_256_GCM_SHA384. public static final Cipher TLS_AES_256_GCM_SHA384 ...

#57. TLS configuration update – disabling of weak cipher suites

Bosch IoT Rollouts: TLS configuration update – disabling of weak cipher suites · TLS_AES_128_GCM_SHA256; TLS_AES_256_GCM_SHA384 ...

#58. It's not possible to change the ciphers for TLSv1.3 when using ...

TLSv1.3 connections that are established by OpenEdge 12.0 can only use the default cipher of TLS_AES_256_GCM_SHA384

#59. Re: nginx 1.17.1 configcheck fails if config'd for TLSv1.3-only ?

TLS_AES_256_GCM_SHA384 Key Exchange Group x25519. Signature Scheme ECDSA-P384-SHA384 switching nginx config ssl_protocols TLSv1.3;

#60. TLS 1.2 vs TLS 1.3 - Performance - Cloudflare Community

... 224 HTTP/1.1 TLSv1.3 TLS_AES_256_GCM_SHA384 Mozilla/5.0 (Macintosh; Intel Mac Gecko) Chrome/74.0.3729.131 Safari/537.36 204 HTTP/1.1 ...

#61. How do I enable TLS 1.3 | DigitalOcean

Enable only secure ciphers: SSLCipherSuite TLSv1.3 TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384 # SSL server ...

#62. Guide to TLS Standards Compliance - SSL.com

TLS 1.3 has a much shorter list of cipher suites: TLS_AES_128_GCM_SHA256 (0x13, 0x01); TLS_AES_256_GCM_SHA384 (0x13, 0x02) ...

#63. SSL_CTX_set_cipher_list(3) - NetBSD Manual Pages

Valid TLSv1.3 ciphersuite names are: TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_CCM_SHA256 ...

#64. client-simulation.wiresharked.txt - testssl.sh

... ciphers+=("TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE- ...

#65. "TLS_AES_256_GCM_SHA384" +jarm - TimeWeb Ltd. - LeakIX

... for "+certificate.cypher_suite:"TLS_AES_256_GCM_SHA384" +jarm:"29d29d15d29d29d21c42d42d000000d740f47fc623495ea334f7291b19b353" +net:"TimeWeb ...

#66. Chrome69/Win7, Firefox62/Win7 Protocol or cipher suite ...

They connect as TLS 1.3 instead of TLS 1.2. | [Chrome 69 / Win 7][1]R | Protocol or cipher suite mismatch 0x7f1c | TLS_AES_256_GCM_SHA384 ...

#67. CipherSuite (Bouncy Castle Library 1.70 API Specification)

static int, TLS_AES_256_GCM_SHA384. static int, TLS_CHACHA20_POLY1305_SHA256. static int, TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA.

#68. 253060 – sendmail submit is unable to verify certificate

... relay=[127.0.0.1], version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256 The fix is to add the following two lines ...

#69. [SOLVED] Issues with Kubernetes IngressRoutes and ...

Accepted TLSv1.3 256 bits TLS_AES_256_GCM_SHA384 Curve 25519 DHE 253. Accepted TLSv1.3 256 bits TLS_CHACHA20_POLY1305_SHA256 Curve 25519 DHE ...

#70. Problem with SMTP Only - Zimbra Forums

... TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256

#71. How to check the SSL/TLS Cipher Suites in Linux and Windows

(it is always DHE or ECDHE). Here are the 5 TLS v1.3 Cipher Suites that are supported by OpenSSL: TLS_AES_256_GCM_SHA384 ...

#72. ITP - Business IT Power Support

TLS_AES_256_GCM_SHA384 (0x1302) ECDH secp384r1 (eq. 7680 bits RSA) FS ... Android 9.0, -, TLS 1.3 TLS_AES_256_GCM_SHA384 ECDH secp384r1 FS.

#73. PAN-OS 10.0 Decryption Cipher Suites - Palo Alto Networks

TLS_AES_256_GCM_SHA384. TLS_CHACHA20_POLY1305_SHA256. TLS_AES_128_GCM_SHA256. SSL/TLS Decryption—NIST-approved Elliptical Curves. P-192 (secp192r1).

#74. TLS v1.3 support issue - DICOM @ OFFIS

TLS_AES_256_GCM_SHA384. TLS_CHACHA20_POLY1305_SHA256. TLS_AES_128_GCM_SHA256. TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.

#75. SSL Report: infosubasta.es Assessed on

TLS_AES_256_GCM_SHA384 (0x1302) ECDH 25519 (eq. 3072 bits RSA) FS. 256. TLS CHACHA2O POLY1305_SHA256 (0x1303) ECDH X25519 (, 3072 bits RSA) ...

#76. Correcting certificate paths - Install & Config

... info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384) Feb 09 21:48:52 c2s5648aa3cd030 info Client disconnected: connection closed ...

#77. How to display details for specific OpenSSL cipher

Set specific ciphersuite and define NULL cipher list. List details for TLS_AES_256_GCM_SHA384 cipher suite. $ openssl ciphers -s -stdname - ...

#78. Frontend TLS1.3 backend TLS1.0 - Help! - HAProxy community

... unable to set TLS 1.3 cipher suites to 'TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384'.

#79. Need Help Connecting to Database - Laracasts

Host: localhost Port: 3306 User: root SSL: enabled with TLS_AES_256_GCM_SHA384 Password: password Database: mytodos. It says "Successfully made the MySQL ...

#80. mailbox.org - TLS / STARTTLS Test · SSL-Tools

Hostname / IP address Priority STARTTLS Certificates mx2.mailbox.org 80.241.60.215 Results incomplete 10 supported not checked TLSv1... mx1.mailbox.org 80.241.60.212 Results incomplete 10 supported not checked TLSv1... mx3.mailbox.org 80.241.60.216 Results incomplete 20 supported not checked TLSv1...

#81. Balena OpenVPN TLS Version - balenaOS - balenaForums

For example, on an RPi 3 I have running, the result is Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA.

#82. Hardening TLS Configuration - 夏樹の時間

... TLS_AES_256_GCM_SHA384 0x13, 0x02 TLS1.3 TLS_CHACHA20_POLY1305_SHA256 0x13, 0x03 TLS1.3 TLS_AES_128_GCM_SHA256 0x13, ...

#83. Standards and platform support - Rebex TLS

TLS_AES_256_GCM_SHA384 (AES/GCM with 256-bit key); TLS_CHACHA20_POLY1305_SHA256 (ChaCha20-Poly1305 AEAD cipher). Use Parameters.SetSymmetricCipherSuites(...) ...

#84. What is the Windows default cipher suite order? - Nartac ...

TLS_AES_256_GCM_SHA384 TLS_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 ...

#85. dovecot TSL 1.3 config option 'ssl_ciphersuites' causes fatal ...

Valid TLSv1.3 ciphersuite names are: TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_CCM_SHA256 ...

#86. Supported hashing and encryption algorithms for TLS libraries

1.2, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384. TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256. TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. 1.3, TLS_AES_256_GCM_SHA384.

#87. Re: Why can't I force a specific cipher with the openssl app ...

... that has one supported cipher, i.e. TLS_AES_256_GCM_SHA384. ... -ciphersuites TLS_AES_256_GCM_SHA384 > > And the server starts up as it ...

#88. SSL/TLS Implementation CIO-IT Security-14-69 - GSA

following FIPS-approved ciphers in this order of preference (from highest to lowest):. 1. TLS_AES_256_GCM_SHA384. 2. TLS_AES_128_GCM_SHA256.

#89. High Security pfSense HAProxy with TLS 1.3 | Stefandroid Blog

... TLSv1.3 Negotiated cipher TLS_AES_256_GCM_SHA384, 253 bit ECDH (X25519) Cipher per protocol Hexcode Cipher Suite Name (OpenSSL) KeyExch.

#90. Standards Compliance - Erlang/OTP

Section State Since 1.3. Updates Affecting TLS 1.2 C 24.1 C 22 C 24.1

#91. Check a DANE TLS Service - Shumon Huque

... TLS version: TLS1.3 CipherSuite: TLS_AES_256_GCM_SHA384 ## End-Entity Certificate Info: X509 version: 3 Serial#: 44221599eb488d1da5012e7d2a547fa5dfa ...

#92. OpenSSL 1.1.1 it supports only 3 out of 5 ciphers TLS 1.3

I have configured everything as it supposed to be, the thing is while TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256, TLS_AES_128_GCM_SHA256 are ...

#93. 18.2. ssl — TLS/SSL wrapper for socket objects - Python 3.7 ...

Changed in version 3.7: TLS 1.3 cipher suites TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, and TLS_CHACHA20_POLY1305_SHA256 were added to the default ...

#94. WildFly Performance Tuning - 第 132 頁 - Google 圖書結果

... cipher-suite-names= "TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256" protocols="TLSv1.3" key-manager="demoKeyManager"/> ...

#95. Learn PostgreSQL: Build and manage high-performance database ...

... cipher: TLS_AES_256_GCM_SHA384, bits: 256, compression: off) Type "help" for help. forumdb=> If you omit the sslmode parameter, or use the standard psql ...

#96. Chapter 1. OpenSSL Command Line - Feisty Duck

TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD ... openssl ciphers -v -s -ciphersuites TLS_AES_256_GCM_SHA384 SEED-SHA ...

#97. Linux Tutorials - Herong's Tutorial Examples

... TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Server public key is 4096 bit Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN ...

#98. Using and Administering Linux: Volume 3: Zero to SysAdmin: ...

... ([192.168.56.21]) by studentvm2.example.com (8.15.2/8.15.2) with ESMTPS id x5TDa0B9004335 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 ...