From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) (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 1D5C521AE30DB for ; Wed, 7 Jun 2017 00:43:03 -0700 (PDT) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2017 00:44:08 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,310,1493708400"; d="scan'208";a="1138795688" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga001.jf.intel.com with ESMTP; 07 Jun 2017 00:44:08 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 7 Jun 2017 00:44:08 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.116]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.197]) with mapi id 14.03.0319.002; Wed, 7 Jun 2017 15:44:06 +0800 From: "Wu, Jiaxin" To: Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: HTTPS boot support questions Thread-Index: AdLfQcZ2XgVygBQPRIaSISlIbUvpFwAGT4+gAACUDhAAAGQ18AAAjwZA Date: Wed, 7 Jun 2017 07:44:05 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B7274162DA39F@SHSMSX103.ccr.corp.intel.com> References: <625A2455CC232F40B0F38F05ACED6D97C869045A@Venus2.in.megatrends.com> <895558F6EA4E3B41AC93A00D163B7274162DA335@SHSMSX103.ccr.corp.intel.com> <625A2455CC232F40B0F38F05ACED6D97C8690558@Venus2.in.megatrends.com> <625A2455CC232F40B0F38F05ACED6D97C8690590@Venus2.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97C8690590@Venus2.in.megatrends.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDQzNzg5OGItMTFhOS00NGU3LTljNjAtY2RlZWNiNDVlOGRmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX1BVQkxJQyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNS45LjYuNiIsIlRydXN0ZWRMYWJlbEhhc2giOiJMZWVkdHVTT1o1S2VwK1JIc2dGb0VuZkFCUVhRd1hCcTU3dzY0YVVMaHo4PSJ9 x-ctpclassification: CTP_PUBLIC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: HTTPS boot support questions 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: Wed, 07 Jun 2017 07:43:03 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Naveen, I mean the WinPE/Windows 10 OS can't be installed via UEFI HTTP(S) feature.= Currently, I only verified the ISO image is SUSE SLES. Thanks, Jiaxin > -----Original Message----- > From: Santhapur Naveen [mailto:naveens@amiindia.co.in] > Sent: Wednesday, June 7, 2017 3:29 PM > To: Santhapur Naveen ; Wu, Jiaxin > ; edk2-devel@lists.01.org > Subject: RE: HTTPS boot support questions >=20 > Hi Jiaxin, >=20 > For #2, you meant server for HTTPS can't be configured in Windows alone o= r > the OS can't be installed over HTTPS? I don't think the latter is valid. = Please > clarify. >=20 > Thanks, > Naveen >=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > Santhapur Naveen > Sent: Wednesday, June 07, 2017 12:43 PM > To: Wu, Jiaxin; edk2-devel@lists.01.org > Subject: Re: [edk2] HTTPS boot support questions >=20 > Hi Jiaxin, >=20 > Thanks for your comments. >=20 > Regards, > Naveen >=20 > -----Original Message----- > From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com] > Sent: Wednesday, June 07, 2017 12:41 PM > To: Santhapur Naveen; edk2-devel@lists.01.org > Subject: RE: HTTPS boot support questions >=20 > Hi Naveen, >=20 > For your question: > #1: Yes, HTTPS Boot can work with port 80, but you have to close any poss= ible > website may be using the same port. >=20 > #2: No, AFAIK, currently, HTTP(S) can't co-work with WinPE/Windows 10 OS > installation. >=20 > #3: Yes, secure boot feature is not related to HTTPS boot. You can finish= the > download process no matter secure boot enabled or not. But the download > image must be signed to continue the execution. >=20 > Thanks, > Jiaxin >=20 >=20 >=20 > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > > Santhapur Naveen > > Sent: Wednesday, June 7, 2017 12:11 PM > > To: edk2-devel@lists.01.org > > Subject: [edk2] HTTPS boot support questions > > > > Hello, > > > > I have some questions regarding HTTPS Boot and are as below. > > > > 1. If I'm using iPXE port 80 to communicate with server because of > > firewall concern. Does https boot happen via the same 80 port? > > 2. Does it support WinPE/Windows 10 OS installation? If yes, is there > > any open document available to achieve the same? > > 3. Does it support network boot without disabling secure boot OS? > > > > Thanks in advance, > > 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 > This e-mail is intended for the use of the addressee only and may contain > privileged, confidential, or proprietary information that is exempt from > disclosure under law. If you have received this message in error, please > inform us promptly by reply e-mail, then delete the e-mail and destroy an= y > printed copy. Thank you.