public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Li, Yi" <yi1.li@intel.com>
To: devel@edk2.groups.io
Cc: Yi Li <yi1.li@intel.com>, Zhichao Gao <zhichao.gao@intel.com>,
	Ming Tan <ming.tan@intel.com>, Heng Luo <heng.luo@intel.com>
Subject: [edk2-staging][PATCH 2/2] CryptoPkg: fix wrong name in tls 1.2 cipher suite
Date: Fri, 24 Feb 2023 14:49:19 +0800	[thread overview]
Message-ID: <81b8a02662ea1d26a4a25b5c0532d2dbc4761092.1677218500.git.yi1.li@intel.com> (raw)
In-Reply-To: <cover.1677218500.git.yi1.li@intel.com>

Keep cipher name consistent with openssl.

Cc: Zhichao Gao <zhichao.gao@intel.com>
Cc: Ming Tan <ming.tan@intel.com>
Cc: Heng Luo <heng.luo@intel.com>
Signed-off-by: Yi Li <yi1.li@intel.com>
---
 CryptoPkg/Library/TlsLib/TlsConfig.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CryptoPkg/Library/TlsLib/TlsConfig.c b/CryptoPkg/Library/TlsLib/TlsConfig.c
index 3a3490c2ac..30247b931b 100644
--- a/CryptoPkg/Library/TlsLib/TlsConfig.c
+++ b/CryptoPkg/Library/TlsLib/TlsConfig.c
@@ -70,8 +70,8 @@ STATIC CONST TLS_CIPHER_MAPPING  TlsCipherMappingTable[] = {
   MAP (0x1302, "TLS_AES_256_GCM_SHA384"),                  /// TLS_AES_256_GCM_SHA384
   MAP (0x1303, "TLS_CHACHA20_POLY1305_SHA256"),            /// TLS_CHACHA20_POLY1305_SHA256
   MAP (0x1301, "TLS_AES_128_GCM_SHA256"),                  /// TLS_AES_128_GCM_SHA256
-  MAP (0xC02B, "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256"), /// TLS_ECDHE_ECDSA_AES128_GCM_SHA256
-  MAP (0xC02C, "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384"), /// TLS_ECDHE_ECDSA_AES256_GCM_SHA384
+  MAP (0xC02B, "ECDHE-ECDSA-AES128-GCM-SHA256"),           /// TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
+  MAP (0xC02C, "ECDHE-ECDSA-AES256-GCM-SHA384"),           /// TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
   MAP (0xC030, "ECDHE-RSA-AES256-GCM-SHA384"),             /// TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 };
 
-- 
2.31.1.windows.1


  parent reply	other threads:[~2023-02-24  6:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  6:49 [edk2-staging][PATCH 0/2] CryptoPkg: openssl submodule update Li, Yi
2023-02-24  6:49 ` [edk2-staging][PATCH 1/2] CryptoPkg: update openssl to 1.1.1t Li, Yi
2023-02-28  8:15   ` Heng Luo
2023-02-24  6:49 ` Li, Yi [this message]
2023-02-28  8:15   ` [edk2-staging][PATCH 2/2] CryptoPkg: fix wrong name in tls 1.2 cipher suite Heng Luo
2023-02-28  8:16 ` [edk2-staging][PATCH 0/2] CryptoPkg: openssl submodule update Heng Luo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81b8a02662ea1d26a4a25b5c0532d2dbc4761092.1677218500.git.yi1.li@intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox