From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on072e.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe42::72e]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 139D91A1E12 for ; Tue, 2 Aug 2016 14:14:12 -0700 (PDT) Received: from TU4PR84MB0159.NAMPRD84.PROD.OUTLOOK.COM (10.162.187.152) by TU4PR84MB0158.NAMPRD84.PROD.OUTLOOK.COM (10.162.187.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.15; Tue, 2 Aug 2016 21:14:09 +0000 Received: from TU4PR84MB0159.NAMPRD84.PROD.OUTLOOK.COM ([10.162.187.152]) by TU4PR84MB0159.NAMPRD84.PROD.OUTLOOK.COM ([10.162.187.152]) with mapi id 15.01.0549.022; Tue, 2 Aug 2016 21:14:09 +0000 From: "Palmer, Thomas" To: "Wu, Jiaxin" , "Long, Qin" , "edk2-devel@lists.01.org" CC: "Ye, Ting" , "Fu, Siyuan" , "Gao, Liming" Thread-Topic: [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS definitions with the standardized one Thread-Index: AQHR3ZPC2hroSCc030eQHf5GuV9O+KAwDRGAgANeIICAAAcoAIABFJKwgAB57ICAAADCIIAABz8AgAExasA= Date: Tue, 2 Aug 2016 21:14:09 +0000 Message-ID: References: <1468475478-145272-1-git-send-email-jiaxin.wu@intel.com> <895558F6EA4E3B41AC93A00D163B7274137C2D07@SHSMSX103.ccr.corp.intel.com> <895558F6EA4E3B41AC93A00D163B7274137C341E@SHSMSX103.ccr.corp.intel.com> <895558F6EA4E3B41AC93A00D163B7274137C3471@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <895558F6EA4E3B41AC93A00D163B7274137C3471@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=thomas.palmer@hpe.com; x-originating-ip: [15.203.227.4] x-ms-office365-filtering-correlation-id: dd1d55db-5384-4d71-d090-08d3bb19f1ee x-microsoft-exchange-diagnostics: 1; TU4PR84MB0158; 6:/zMc1DikMIxL9kO6CEnHsj1tYBJc7EiNQf1GF6jVv7BusF3/i/4n5b8ocFZXYnzI0j0zI+Q0ObUX5hADJmUwLns9InE+oe9fbXi69nYkukWzDVoMNqTDw9ZmwXKh7H1k+Ht7GOaXgML+bX3SFMQzEkGb+O+hsyycO5SBFqtKS4J/rPtJCuflC8PkHKV9WI6FB3vEhSADjVrhA/wFEmkLcLUIHA4Ts50GpSk4hJifIJ/Ab4dygZOgSNNeita95I0zM952OM9e5qoD+qD7uI+lzb/aYOlEB2N6LePlu+17Y2c2SsoM9tPqKKAQIbjDNR1z6sHL77YiDky38HI+hT5Sbg==; 5:cAZivaYZZm7PymxgR4kN/oWEs/bVNi8u0IvunP3YqNShmUtyy5sQjbH3O5TlILJXXM5VGlzgGPvQQgWzkbBEwbV+/Qf6i+duCeeQq7Coz2KVVhcqc8bWQPvUukTtAg6X8FD7ik2Pwa3MWt7/6LYChQ==; 24:kpEeog3fWVnVNil7PL6gG8ADAvTc1f89a8WkdvycWI25k9cmLQ3n1E1gJyc1j0HtKkOWg0vhmF26rB+H3OVR9ucjk3FpipfaVg8CmzQaDlg=; 7:sZpgGFUbxuPi8YDbgQBZyu1fXDzP/4kwQAZ7D2rqVuZ1dumXyl+r4r/lTWxhuyvpCPOCOY4xAG2ATkpIrcYRsNPNOZSmuezWDNuSsFzCaJxyPKi3G96X2J+N8ZRxSSBPoy9NdvZ5n1Xl/BMbTzBVc6iNTnXxKSSGFIV1sIBM9UFOawoBg96twZvSQzV1ywRlMqW6rTTs6NlFeFQbh4X4ke+pwiOSSF92L/+uI3ngoEqmp99OkZ6eYWZfP7pZqw7d x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TU4PR84MB0158; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(227479698468861)(65766998875637)(788757137089)(162533806227266)(36789356921836)(228905959029699); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026); SRVR:TU4PR84MB0158; BCL:0; PCL:0; RULEID:; SRVR:TU4PR84MB0158; x-forefront-prvs: 0022134A87 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(199003)(13464003)(377454003)(189002)(19580405001)(305945005)(19580395003)(6116002)(189998001)(99286002)(10400500002)(2501003)(7736002)(93886004)(7696003)(102836003)(3846002)(5002640100001)(561944003)(33656002)(5001770100001)(105586002)(7846002)(101416001)(50986999)(74316002)(97736004)(86362001)(76176999)(54356999)(106356001)(81166006)(2906002)(77096005)(66066001)(3280700002)(3900700001)(3660700001)(122556002)(81156014)(8936002)(586003)(8676002)(68736007)(15975445007)(92566002)(87936001)(9686002)(2900100001)(2950100001)(106116001)(4326007)(11100500001)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:TU4PR84MB0158; H:TU4PR84MB0159.NAMPRD84.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: hpe.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: hpe.com X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Aug 2016 21:14:09.5367 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc X-MS-Exchange-Transport-CrossTenantHeadersStamped: TU4PR84MB0158 Subject: Re: [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS definitions with the standardized one X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2016 21:14:12 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have two sets of lists, one for the ciphers the OpenSSL by default confi= gures in a new CTX and the other after setting all ciphers available in the= mapping table. For both sets I show the affect of removing no-idea/no-dsa= and adding enable-weak-ciphers These are the ciphers that are supported by TLS immediately after a TLS_CTX= _new operation with current OpenSSL config (34): AES128-GCM-SHA256 AES128-SHA AES128-SHA256 AES256-GCM-SHA384 AES256-SHA AES256-SHA256 DES-CBC3-SHA DH-DSS-AES128-GCM-SHA256 DH-DSS-AES128-SHA DH-DSS-AES128-SHA256 DH-DSS-AES256-GCM-SHA384 DH-DSS-AES256-SHA DH-DSS-AES256-SHA256 DH-DSS-DES-CBC3-SHA DHE-RSA-AES128-GCM-SHA256 DHE-RSA-AES128-SHA DHE-RSA-AES128-SHA256 DHE-RSA-AES256-GCM-SHA384 DHE-RSA-AES256-SHA DHE-RSA-AES256-SHA256 DH-RSA-AES128-GCM-SHA256 DH-RSA-AES128-SHA DH-RSA-AES128-SHA256 DH-RSA-AES256-GCM-SHA384 DH-RSA-AES256-SHA DH-RSA-AES256-SHA256 DH-RSA-DES-CBC3-SHA EDH-RSA-DES-CBC3-SHA PSK-3DES-EDE-CBC-SHA PSK-AES128-CBC-SHA PSK-AES256-CBC-SHA PSK-RC4-SHA RC4-MD5 RC4-SHA By removing "no-idea" in process_files we gain (1): IDEA-CBC-SHA By removing "no-dsa" in process_files we gain (7): DHE-DSS-AES128-GCM-SHA256 DHE-DSS-AES128-SHA DHE-DSS-AES128-SHA256 DHE-DSS-AES256-GCM-SHA384 DHE-DSS-AES256-SHA DHE-DSS-AES256-SHA256 EDH-DSS-DES-CBC3-SHA We do not gain any more ciphers with enable-weak-ssl-ciphers at this point. Now here are the ciphers after TlsSetCipherList has been run with setting a= ll ciphers currently in TlsCipherMappingTable. With original OpenSSL configuration (23): AES128-SHA AES128-SHA256 AES256-SHA AES256-SHA256 DES-CBC3-SHA DH-DSS-AES128-SHA DH-DSS-AES128-SHA256 DH-DSS-AES256-SHA DH-DSS-AES256-SHA256 DHE-RSA-AES128-SHA DHE-RSA-AES128-SHA256 DHE-RSA-AES256-SHA DHE-RSA-AES256-SHA256 DH-RSA-AES128-SHA DH-RSA-AES128-SHA256 DH-RSA-AES256-SHA DH-RSA-AES256-SHA256 EDH-RSA-DES-CBC3-SHA NULL-MD5 NULL-SHA NULL-SHA256 RC4-MD5 RC4-SHA By removing "no-idea" in process_files we gain (1): IDEA-CBC-SHA By removing "no-dsa" in process_files we gain (5): DHE-DSS-AES256-SHA DHE-DSS-AES256-SHA256 DHE-DSS-AES128-SHA DHE-DSS-AES128-SHA256 EDH-DSS-DES-CBC3-SHA Be adding enable-weak-ssl-ciphers we gain (1): DES-CBC-SHA Thomas -----Original Message----- From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com]=20 Sent: Monday, August 1, 2016 9:03 PM To: Palmer, Thomas ; Long, Qin ;= edk2-devel@lists.01.org Cc: Ye, Ting ; Fu, Siyuan ; Gao, Li= ming Subject: RE: [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS definitions wit= h the standardized one Thomas, Thanks your effort to test the new ciphers, can you provide the info which = one is unsupported currently? As Qin's comments, "we'd better to keep the current supported cipher suite = for our UEFI- TLS enabling". If so, I agree to remove the unsupported one i= n TlsCipherMappingTable instead of changing the current openssl configurati= on. If dsa /idea is required in future, then we can consider how to enable = the configuration. So, can you provide the patch to remove the unsupported one in TlsCipherMap= pingTable? Thanks, Jiaxin > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of=20 > Palmer, Thomas > Sent: Tuesday, August 2, 2016 9:51 AM > To: Wu, Jiaxin ; Long, Qin ;=20 > edk2-devel@lists.01.org > Cc: Ye, Ting ; Fu, Siyuan ;=20 > Gao, Liming > Subject: Re: [edk2] [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS=20 > definitions with the standardized one >=20 >=20 > Hi Jiaxin, >=20 > It sounds like we both agree that TlsCipherMappingTable is the list=20 > of what UEFI officially supports. If it is advertised in=20 > TlsCipherMappingTable then OpenSSL needs to support it. >=20 > My proposal of removing no-dsa / no-idea and adding weak-ciphers is=20 > specifically aimed to syncing how OpenSSL is configured/built to what=20 > is in TlsCipherMappingTable. I was busy last week testing out the new=20 > ciphers and realized a few were not even getting configured in OpenSSL. >=20 > Thomas >=20 > -----Original Message----- > From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com] > Sent: Monday, August 1, 2016 8:34 PM > To: Palmer, Thomas ; Long, Qin=20 > ; edk2-devel@lists.01.org > Cc: Ye, Ting ; Fu, Siyuan ;=20 > Gao, Liming > Subject: RE: [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS=20 > definitions with the standardized one >=20 > Hi Thomas, >=20 > Since the Tls1.h is used to hold the standardized definitions, openssl=20 > part is not taken into consideration. The Cipher Suites added in=20 > Tls1.h only refers to > A.5 of rfc-2246, rfc-4346 and rfc-5246. The criteria is removing all=20 > the limited/insecurity/deprecated ones that specified in RFC -- "Note=20 > that this mode is vulnerable to man-in-the middle attacks and is=20 > therefore deprecated." I know the IDEA and DES cipher suites are also=20 > deprecated in TLS1.2, but it does means to TLS1.1. So, some of them are s= till kept in Tls1.h. >=20 > As for the TlsCipherMappingTable, it takes on the link between Tls1.h=20 > defined cipher suites and openssl supported cipher suites. If we=20 > eliminate the factors of configuration, I believe the cipher suites in=20 > TlsCipherMappingTable should be implemented in OpenSSL lib. I haven't=20 > check them one by one but openssl official document is referred @=20 > https://www.openssl.org/docs/manmaster/apps/ciphers.html, which gives=20 > the lists of TLS cipher suites names from the relevant specification=20 > and their OpenSSL equivalents. >=20 > If the cipher suites in Tls1.h is not found in TlsCipherMappingTable,=20 > EFI_UNSUPPORTED will be returned. I think it's reasonable. >=20 > Thanks, > Jiaxin >=20 > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf=20 > > Of Palmer, Thomas > > Sent: Tuesday, August 2, 2016 5:46 AM > > To: Long, Qin ; Wu, Jiaxin=20 > > ; edk2-devel@lists.01.org > > Cc: Ye, Ting ; Fu, Siyuan ;=20 > > Gao, Liming > > Subject: Re: [edk2] [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS=20 > > definitions with the standardized one > > > > Jiaxin / Qin, > > > > > > I'm unaware of what criteria is required for a cipher to be in this=20 > > TlsCipherMappingTable. I had presumed that it would be b/c UEFI=20 > > supported the cipher for TLS operation. If unsupported ciphers are=20 > > allowed ... then logically wouldn't we need to add all ciphers? =20 > > What advantage do we gain by having an entry in this table but not=20 > > actually use > the cipher in communication? > > > > Currently TlsGetCipherString is the only means we have to validate=20 > > the cipher string. If a cipher is in the table but not in OpenSSL=20 > > lib, then we will provide imperfect feedback if the unsupported=20 > > cipher is buried in a list of supported ciphers. OpenSSL will=20 > > simply use only the ciphers it supports and quietly drop the unsupporte= d cipher. > > A user that inspects the list of set ciphers would be curious why a=20 > > certain > cipher was being "dropped" / > > "filtered". However, if TlsGetCipherString sees that the cipher is no= t in our > > mapping table the TlsSetCipherList function will return immediate feedb= ack. > > > > I'm not enthralled with supporting weak/idea ciphers either. I=20 > > would vouch for us removing those ciphers from=20 > > TlsCipherMappingTable. It is not our responsibility to document the=20 > > IANA/Description string description in code. > > > > This document > > (http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-52 > > r1 > > .pdf) would be a good list for initial cipher support. We have some=20 > > of the ciphers on the list already. Here is the sorted list: > > > > TLS_DH_DSS_WITH_3DES_EDE_CBC_SHA > > TLS_DH_DSS_WITH_AES_128_CBC_SHA > > TLS_DH_DSS_WITH_AES_128_CBC_SHA256 > > TLS_DH_DSS_WITH_AES_128_GCM_SHA256 > > TLS_DH_DSS_WITH_AES_256_CBC_SHA > > TLS_DH_DSS_WITH_AES_256_CBC_SHA256 > > TLS_DH_DSS_WITH_AES_256_GCM_SHA384 > > TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA > > TLS_DHE_DSS_WITH_AES_128_CBC_SHA > > TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 > > TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 > > TLS_DHE_DSS_WITH_AES_256_CBC_SHA > > TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 > > TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 > > TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA > > TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA > > TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 > > TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256 > > TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA > > TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384 > > TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 > > TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA > > TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA > > TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 > > TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 > > TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA > > TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 > > TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 > > TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA > > TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA > > TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 > > TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 > > TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA > > TLS_RSA_WITH_3DES_EDE_CBC_SHA > > TLS_RSA_WITH_AES_128_CBC_SHA > > TLS_RSA_WITH_AES_128_CBC_SHA256 > > TLS_RSA_WITH_AES_128_CCM17 > > TLS_RSA_WITH_AES_128_GCM_SHA256 > > TLS_RSA_WITH_AES_256_CBC_SHA > > TLS_RSA_WITH_AES_256_CBC_SHA256 > > TLS_RSA_WITH_AES_256_CCM > > TLS_RSA_WITH_AES_256_GCM_SHA384 > > > > Thomas > > > > -----Original Message----- > > From: Long, Qin [mailto:qin.long@intel.com] > > Sent: Sunday, July 31, 2016 8:48 PM > > To: Wu, Jiaxin ; Palmer, Thomas=20 > > ; edk2-devel@lists.01.org > > Cc: Ye, Ting ; Fu, Siyuan ;=20 > > Gao, Liming > > Subject: RE: [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS=20 > > definitions with the standardized one > > > > I personally prefer to keep the current supported cipher suite for=20 > > our > > UEFI- TLS enabling. We can have the full RFC definitions, and=20 > > platform specific cipher sets for validation now. It's better to=20 > > maintain one minimal scope in this phase. > > > > "enable-weak-ssl-ciphers" looks odd. Disabling weak ciphers is the=20 > > recommendation for hardening SSL communications. > > For other ciphers (idea, dsa, etc), we can enable them step-by-step=20 > > depending on the real requirements. > > > > > > Best Regards & Thanks, > > LONG, Qin > > > > > -----Original Message----- > > > From: Wu, Jiaxin > > > Sent: Monday, August 01, 2016 9:23 AM > > > To: Palmer, Thomas; Long, Qin; edk2-devel@lists.01.org > > > Cc: Ye, Ting; Fu, Siyuan; Gao, Liming > > > Subject: RE: [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS=20 > > > definitions with the standardized one > > > > > > Thomas, > > > I agree some of them are not supported due to the UEFI OpenSSL=20 > > > configuration, but it doesn't affect those mapping relationship=20 > > > added in the patch. So, I have no strong opinion whether to=20 > > > support it by modifying the current OpenSSL configuration. Since=20 > > > Qin is the OpenSSL expert, I'd like to hear his views. > > > > > > Qin, > > > What's your opinion? > > > > > > Thanks. > > > Jiaxin > > > > > > > -----Original Message----- > > > > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On=20 > > > > Behalf Of Palmer, Thomas > > > > Sent: Saturday, July 30, 2016 6:03 AM > > > > To: Wu, Jiaxin ; edk2-devel@lists.01.org > > > > Cc: Ye, Ting ; Fu, Siyuan=20 > > > > ; Gao, Liming ; Long,=20 > > > > Qin > > > > Subject: Re: [edk2] [staging/HTTPS-TLS][PATCH 0/4] Replace the=20 > > > > TLS definitions with the standardized one > > > > > > > > Jiaxin, > > > > > > > > UEFI's OpenSSL library does not support all the ciphers that=20 > > > > were added in your patch due to the UEFI configuration. We need=20 > > > > to remove > > > > "no- idea" and "no-dsa" from the process_files.sh and add > > > > "enable-weak-ssl- ciphers" > > > > > > > > While we are modifying process_files.sh, we can remove "no- > > > pqueue" > > > > from process_files.sh so that OpensslLib.inf is in sync. > > > > > > > > I can send out a patch to do so if you wish. > > > > > > > > Thomas > > > > > > > > -----Original Message----- > > > > From: Jiaxin Wu [mailto:jiaxin.wu@intel.com] > > > > Sent: Thursday, July 14, 2016 12:51 AM > > > > To: edk2-devel@lists.01.org > > > > Cc: Liming Gao ; Palmer, Thomas=20 > > > > ; Long Qin ; Ye Ting=20 > > > > ; Fu Siyuan ; Wu Jiaxin=20 > > > > > > > > Subject: [staging/HTTPS-TLS][PATCH 0/4] Replace the TLS=20 > > > > definitions with the standardized one > > > > > > > > The series patches are used to replace the TLS definitions with=20 > > > > the standardized one. In addition, more TLS cipher suite mapping=20 > > > > between Cipher Suite definitions and OpenSSL-used Cipher Suite=20 > > > > name > are added. > > > > > > > > Cc: Liming Gao > > > > Cc: Palmer Thomas > > > > Cc: Long Qin > > > > Cc: Ye Ting > > > > Cc: Fu Siyuan > > > > Contributed-under: TianoCore Contribution Agreement 1.0 > > > > Signed-off-by: Wu Jiaxin > > > > Signed-off-by: Jiaxin Wu > > > > > > > > Jiaxin Wu (4): > > > > MdePkg: Add a header to standardize TLS definitions > > > > CryptoPkg: Add more TLS cipher suite mapping > > > > NetworkPkg/TlsDxe: Replace the definitions with the=20 > > > > standardized > one > > > > NetworkPkg/HttpDxe: Replace the definitions with the=20 > > > > standardized one > > > > > > > > CryptoPkg/Library/TlsLib/TlsLib.c | 3585 ++++++++++++++++----= ----- > --- > > -- > > > -- > > > > MdePkg/Include/IndustryStandard/Tls1.h | 93 + > > > > NetworkPkg/HttpDxe/HttpDriver.h | 2 + > > > > NetworkPkg/HttpDxe/HttpProto.c | 12 +- > > > > NetworkPkg/HttpDxe/HttpsSupport.c | 22 +- > > > > NetworkPkg/HttpDxe/HttpsSupport.h | 44 - > > > > NetworkPkg/TlsDxe/TlsImpl.c | 56 +- > > > > NetworkPkg/TlsDxe/TlsImpl.h | 30 +- > > > > NetworkPkg/TlsDxe/TlsProtocol.c | 2 +- > > > > 9 files changed, 1945 insertions(+), 1901 deletions(-) create=20 > > > > mode > > > > 100644 MdePkg/Include/IndustryStandard/Tls1.h > > > > > > > > -- > > > > 1.9.5.msysgit.1 > > > > > > > > _______________________________________________ > > > > edk2-devel mailing list > > > > edk2-devel@lists.01.org > > > > https://lists.01.org/mailman/listinfo/edk2-devel > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel