From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from IMSVA.IN.MEGATRENDS.COM (venus.amiindia.co.in [111.93.197.227]) (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 4B1271A1F48 for ; Thu, 22 Sep 2016 07:06:46 -0700 (PDT) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8085C8204A; Thu, 22 Sep 2016 19:37:03 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7447D82046; Thu, 22 Sep 2016 19:37:02 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Thu, 22 Sep 2016 19:37:02 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Thu, 22 Sep 2016 19:36:24 +0530 From: Santhapur Naveen To: "Palmer, Thomas" , "edk2-devel@lists.01.org" Thread-Topic: Issues with HTTPS Boot Thread-Index: AdITMrB9dQ9WWubnSXaJO1RcrMRFRgAJIYwAACb2LMAAEohmMAAmfOIw Date: Thu, 22 Sep 2016 14:06:40 +0000 Message-ID: <625A2455CC232F40B0F38F05ACED6D978C2C2C5E@VENUS1.in.megatrends.com> References: <625A2455CC232F40B0F38F05ACED6D978C2C2225@VENUS1.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D978C2C29FD@VENUS1.in.megatrends.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.93.16] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1054-22592.007 X-TM-AS-Result: No--21.486-5.0-31-10 X-imss-scan-details: No--21.486-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1054-22592.007 X-TMASE-Result: 10--21.486100-10.000000 X-TMASE-MatchedRID: vbSD0OnL8/KI0KPyMNrNUrxygpRxo469ju+GX08gELDUMPKrRLOfYTQv iEQoVEjeyruGZXxr2OTmFb4v6eBYPHqSLwsG0mU0nbUZkYTzXIY026H7nOZLrx6ZuDpm2YZnp7u eaEkDqTNe9N8X0ShXYB583oSmrpYBWCHuL6bplKji3aa5wOREESSF0LR+PMPIRoS5c9eVHmqqvf dLlzhiCW+jMrUPdeMEKeruLNnTFHVB0P6WAMIbOgRH1Nr7oERdEtdrY/Wb3fNVaiL9Jo7jBhuCq m239cCo3f0e/BgwI9B1PZ05jmptqYq/kHiC6YFZEe5D10MltLYGAD6h6FZmEbA70W2CHgeK219h x52wweCzRat1Mo03O1qO8woZws6UJol1F8fRTeWpuD25aEtgt/aS52LUPfcS51ONI4UL++qjxYy RBa/qJeGf7whhst7+jaPj0W1qn0TeqVfLTqWfdkyDMs8HUy62 X-TMASE-SNAP-Result: 1.811037.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 Subject: Re: Issues with HTTPS Boot 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: Thu, 22 Sep 2016 14:06:46 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Thomas, Regarding your previous question about the server certificates, please fin= d my response as below: Do you have the appropriate certificate installed in UEFI for the target TL= S server? Yes, I do have the appropriate certificate installed on my server. I have = followed the section 2.2 titles " Self-Generated Certificate" in the white = paper to generate the certificates. I have debugged a bit further and went inside TlsConnectSession() to see = where exactly it is failing and I found out like it fails in TlsDoHandshake= () and gives PROTOCOL ERROR. To be precise, it gives error as "TlsDoHandsha= ke ERROR 0x14171105=3DL14:F171:R105". If I'm missing anything anywhere, would you please provide your comments. Thank you, Naveen -----Original Message----- From: Palmer, Thomas [mailto:thomas.palmer@hpe.com]=20 Sent: Thursday, September 22, 2016 12:56 AM To: Santhapur Naveen; edk2-devel@lists.01.org Subject: RE: Issues with HTTPS Boot >>From what you describe, it sounds like they should not have an issue negoti= ating TLS version and cipher. Do you have the appropriate certificate installed in UEFI for the target TL= S server? Either we need the 3rd part CA that signed the web server certi= ficate, or you could install the self-signed certificate of the web server. Also, are you able to see the any DEBUG statements from TlsLib.c? Regards, Thomas Palmer "I have only made this letter longer because I have not had the time to mak= e it shorter" - Blaise Pascal -----Original Message----- From: Santhapur Naveen [mailto:naveens@amiindia.co.in]=20 Sent: Wednesday, September 21, 2016 8:09 AM To: Palmer, Thomas ; edk2-devel@lists.01.org Subject: RE: Issues with HTTPS Boot Hi Thomas, Regarding my previous mail, after TCP handshake, Client Says Hello to seve= r and the Server replies its Hello to the client with TLSv1. =20 Client says hello with the following Cipher Suites: 1. TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) 2. TLS_DHE_RSA_WITH_AES_128_CB= C_SHA (0x0033) 3. TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) 4. TLS_RSA_WITH_AES= _128_CBC_SHA (0x002f) 5. TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff) For the Client Hello, Server responds with its Hello and chooses TLS_RSA_W= ITH_AES_128_CBC_SHA (0x002f) using TLSv1. The client sends an acknowledgeme= nt to the server and then immediately sends RST.=20 After some debugging, it was found that it fails in TlsConnectSession(). W= ould you please provide your comments on this? Thanks, Naveen -----Original Message----- From: Palmer, Thomas [mailto:thomas.palmer@hpe.com] Sent: Tuesday, September 20, 2016 9:30 PM To: Santhapur Naveen; edk2-devel@lists.01.org Subject: RE: Issues with HTTPS Boot Naveen, I cannot see attachments on this email.=20 =09 What TLS versions and ciphers does your web server support? Depending on w= hen you built the UEFI image, your server may need to have TLS v1.0 enabled= and support one of the non-SHA256 ciphers listed at the top of TlsLib.c. = =20 =09 Regards, Thomas Palmer "I have only made this letter longer because I have not had the time to mak= e it shorter" - Blaise Pascal -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Tuesday, September 20, 2016 6:42 AM To: edk2-devel@lists.01.org Subject: [edk2] Issues with HTTPS Boot Hello All, Since the HTTPS Boot came into picture, I was very enthusiastic t= o try it. I configured the server as-is explained in the white paper https:= //github.com/tianocore/tianocore.github.io/wiki/EDK%20II%20White%20papers But when I try to go for an HTTPS boot, it stops after the TCP ha= ndshake. Attached is the Wireshark log. Please help me out and also let me = know if any other details are needed. Thank you, Naveen _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel