From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (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 192881A1F84 for ; Thu, 22 Sep 2016 23:54:44 -0700 (PDT) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP; 22 Sep 2016 23:54:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,380,1470726000"; d="scan'208";a="12488007" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga005.jf.intel.com with ESMTP; 22 Sep 2016 23:54:43 -0700 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 22 Sep 2016 23:54:43 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx156.amr.corp.intel.com (10.18.116.74) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 22 Sep 2016 23:54:42 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.234]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.118]) with mapi id 14.03.0248.002; Fri, 23 Sep 2016 14:54:40 +0800 From: "Wu, Jiaxin" To: "Palmer, Thomas" , Samer El Haj Mahmoud , Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: Issues with HTTPS Boot Thread-Index: AdITMrB9dQ9WWubnSXaJO1RcrMRFRgAJIYwAACb2LMAAEohmMAAmfOIwAAMjFEAABJQ6AAAZXFlg Date: Fri, 23 Sep 2016 06:54:40 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B727413889028@SHSMSX103.ccr.corp.intel.com> References: <625A2455CC232F40B0F38F05ACED6D978C2C2225@VENUS1.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D978C2C29FD@VENUS1.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D978C2C2C5E@VENUS1.in.megatrends.com> <54EF1A77C479D840AF005ED34A3DC6597041C6@USMAILMBX02> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOWYyZTVlMWItNTAxMy00OGZjLWJkYzgtZjAyYjE2NzQwZGY2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6ImZLYWZDaW43a01DeHJLN2YrT24yb0U2U3ZiSDNnQVp2YVkxRjBhWHBhTEU9In0= x-ctpclassification: CTP_IC x-originating-ip: [10.239.127.40] MIME-Version: 1.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: Fri, 23 Sep 2016 06:54:44 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Naveen, For error code L14:F171:R105, it seems not failed in the ssl3_get_server_he= llo(). L14 means SLL lib error, R105 means SSL_R_WRONG_CIPHER_RETURNED, but= for F171, I can't find the corresponding error function represented. Can y= ou tell us the openssl version your platform used? and what's the cipher re= turned from server hello?=20 Thanks, Jiaxin > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > Palmer, Thomas > Sent: Friday, September 23, 2016 2:10 AM > To: Samer El Haj Mahmoud ; Santhapur Naveen > ; edk2-devel@lists.01.org > Subject: Re: [edk2] Issues with HTTPS Boot >=20 >=20 > Naveen, >=20 > I may be interpreting this OpenSSL error code incorrectly, so if anyone h= as > experience with this please chime in ... >=20 > Looking at 1.02.h, the 0x105 reason corresponds with > SSL_R_WRONG_CIPHER_RETURNED. This happens in two places in s3_clnt.c. > This would indicate that the TLS server is wanting to use a cipher that t= he TLS > client does not want to use. >=20 > 0x105 can also correspond to SSL_F_DTLS1_SEND_CLIENT_CERTIFICATE ... but > we don't support client certificates or DTLS at this point so I would not= expect > this to be in play. (unless your server is configured for that ...) >=20 > We should confirm this error code interpretation. If you have a debugger= , set a > break point for each instance of SSL_R_WRONG_CIPHER_RETURNED, or add a > print statement. Which openssl version are you using? >=20 >=20 > Regards, >=20 > Thomas Palmer >=20 > "I have only made this letter longer because I have not had the time to m= ake it > shorter" - Blaise Pascal >=20 >=20 > -----Original Message----- > From: Samer El Haj Mahmoud [mailto:smahmoud@lenovo.com] > Sent: Thursday, September 22, 2016 10:12 AM > To: Santhapur Naveen ; Palmer, Thomas > ; edk2-devel@lists.01.org > Subject: RE: Issues with HTTPS Boot >=20 > Naveen, >=20 > Are you using the latest code form the edk2-staging branch? >=20 >=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > Santhapur Naveen > Sent: Thursday, September 22, 2016 7:07 AM > To: Palmer, Thomas ; edk2-devel@lists.01.org > Subject: Re: [edk2] Issues with HTTPS Boot >=20 > Hi Thomas, >=20 > Regarding your previous question about the server certificates, please > find my response as below: >=20 > Do you have the appropriate certificate installed in UEFI for the target = TLS > server? > Yes, I do have the appropriate certificate installed on my server. I hav= e > followed the section 2.2 titles " Self-Generated Certificate" in the whit= e paper > to generate the certificates. >=20 > 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 TlsDoHan= dshake() > and gives PROTOCOL ERROR. To be precise, it gives error as "TlsDoHandshak= e > ERROR 0x14171105=3DL14:F171:R105". >=20 > If I'm missing anything anywhere, would you please provide your > comments. >=20 > Thank you, > Naveen >=20 > -----Original Message----- > From: Palmer, Thomas [mailto:thomas.palmer@hpe.com] > Sent: Thursday, September 22, 2016 12:56 AM > To: Santhapur Naveen; edk2-devel@lists.01.org > Subject: RE: Issues with HTTPS Boot >=20 >=20 > From what you describe, it sounds like they should not have an issue > negotiating TLS version and cipher. >=20 >=20 > Do you have the appropriate certificate installed in UEFI for the target = TLS > 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. >=20 > Also, are you able to see the any DEBUG statements from TlsLib.c? >=20 >=20 > Regards, >=20 > Thomas Palmer >=20 > "I have only made this letter longer because I have not had the time to m= ake it > shorter" - Blaise Pascal >=20 > -----Original Message----- > From: Santhapur Naveen [mailto:naveens@amiindia.co.in] > Sent: Wednesday, September 21, 2016 8:09 AM > To: Palmer, Thomas ; edk2-devel@lists.01.org > Subject: RE: Issues with HTTPS Boot >=20 > Hi Thomas, >=20 > Regarding my previous mail, after TCP handshake, Client Says Hello to > sever and the Server replies its Hello to the client with TLSv1. >=20 > Client says hello with the following Cipher Suites: >=20 > 1. TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) 2. > TLS_DHE_RSA_WITH_AES_128_CBC_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) >=20 > For the Client Hello, Server responds with its Hello and chooses > TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) using TLSv1. The client sends an > acknowledgement to the server and then immediately sends RST. >=20 > After some debugging, it was found that it fails in TlsConnectSession(). > Would you please provide your comments on this? >=20 >=20 > Thanks, > Naveen >=20 > -----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 >=20 > Naveen, >=20 > I cannot see attachments on this email. >=20 > What TLS versions and ciphers does your web server support? > Depending on when 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 >=20 > Regards, >=20 > Thomas Palmer >=20 > "I have only made this letter longer because I have not had the time to m= ake it > shorter" - Blaise Pascal >=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > Santhapur Naveen > Sent: Tuesday, September 20, 2016 6:42 AM > To: edk2-devel@lists.01.org > Subject: [edk2] Issues with HTTPS Boot >=20 > Hello All, >=20 > Since the HTTPS Boot came into picture, I was very enthusiastic= to try it. I > configured the server as-is explained in the white paper > https://github.com/tianocore/tianocore.github.io/wiki/EDK%20II%20White%20= p > apers >=20 > But when I try to go for an HTTPS boot, it stops after the TCP = handshake. > Attached is the Wireshark log. Please help me out and also let me know if= any > other details are needed. >=20 > Thank you, > Naveen > _______________________________________________ > 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