From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.43; helo=mga05.intel.com; envelope-from=jiaxin.wu@intel.com; receiver=edk2-devel@lists.01.org Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 7EBE921A134A8 for ; Thu, 16 Nov 2017 16:27:17 -0800 (PST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Nov 2017 16:31:27 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,405,1505804400"; d="scan'208,217";a="174463659" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga005.jf.intel.com with ESMTP; 16 Nov 2017 16:31:26 -0800 Received: from fmsmsx116.amr.corp.intel.com (10.18.116.20) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 16 Nov 2017 16:31:26 -0800 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx116.amr.corp.intel.com (10.18.116.20) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 16 Nov 2017 16:31:25 -0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.213]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.159]) with mapi id 14.03.0319.002; Fri, 17 Nov 2017 08:31:23 +0800 From: "Wu, Jiaxin" To: Karunakar P , "'edk2-devel@lists.01.org'" CC: "Fu, Siyuan" , "Ye, Ting" Thread-Topic: SCT Test crashes After HTTPS boot success. Thread-Index: AdNetw87ERZA5RTMTjO2Kk3mB+3gDwAg7MVg Date: Fri, 17 Nov 2017 00:31:23 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B727416348F70@SHSMSX103.ccr.corp.intel.com> References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOWE5ZDg1MTItYWQ1Ny00NGQ5LWJmNWYtM2U2ZmFmZDVmNDdjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IlBqTThCM3laNG03RFFxeTZQMHFWTlg2N0NUekR2cTJmc1g4MDBiREhKV0U9In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: Re: SCT Test crashes After HTTPS boot success. X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2017 00:27:17 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Karunakar, Can you provide more detailed info for the SCT test steps? The crash can ha= ppen after "Sct.efi -u" or need run any specific test case? Thanks, Jiaxin From: Karunakar P [mailto:karunakarp@amiindia.co.in] Sent: Thursday, November 16, 2017 4:48 PM To: 'edk2-devel@lists.01.org' Cc: Wu, Jiaxin ; Fu, Siyuan ; Ye,= Ting Subject: SCT Test crashes After HTTPS boot success. Hello All, When I do SCT test, get the below failure GenericTest\EFICompliantTest 0 0 CB6F7B77-0B15-43F7-A95B-8C7F9FD70B21 FAIL = UEFI Compliant - TLS support is required The reason for the failure is that the platform doesn't have TLS related pr= otocols installed. ->if the platform supports TLS feature then, EFI_TLS_PROTOCOL, EFI_TLS_SERV= ICE_BINDING_PROTOCOL, EFI_TLS_CONFIGURATION_PROTOCOL must be existed. -> According UEFI2.7 Spec - 28.10 EFI TLS Protocols(page-1787) The TLS consumer need locate EFI_TLS_SERVICE_BINDING_PROTOCOL and call Crea= teChild() to create a new child of EFI_TLS_PROTOCOL instance. Then use EFI_= TLS_PROTOCOL to start TLS session. After use, the TLS consumer need call De= stroyChild() to destroy it. -> Network Stack follows same in HTTPS boot. While doing IPv4/6 HTTPS boot , will locate gEfiTlsServiceBindingProtocolGu= id and call TlsServiceBindingCreateChild, So that EFI_TLS_PROTOCOL and EFI_= TLS_CONFIGURATION_PROTOCOL will be installed. So once HTTPS boot is success then TLS supported protocols exist. And if we do SCT test after HTTPS boot is success, Then TLS related failure= s should NOT happen in SCT. I've tried SCT test after HTTPS boot success, But SCT test Crashes. [Steps to reproduce] 1. Configure the HTTPS Server with EFI Shell as NBP file. 2. Connect test machine and HTTPS server with LAN cable. 3. Perform HTTPS boot in test machine 4. Once HTTPS boot is success, It will launch Shell. 5. Run SCT test [Observations] 1. SCT test was crashed and unable to continue the test. Could you please provide your comments/Suggestion on this? Thanks, Karunakar