<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SGX platforms are not pre in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Initial-SGX-provisioning/m-p/1093583#M909</link>
    <description>&lt;P&gt;SGX platforms are not pre-provisioned.&lt;/P&gt;

&lt;P&gt;Provisioning is triggered as part of the attestation process. &amp;nbsp;When a SGX client application connects to the application server for the first time, the application server will trigger a challenge to the client to attest (running on a valid SGX client machine as well as verifying the validity of enclave running on the client).&lt;/P&gt;

&lt;P&gt;The SGX Platform Software (PSW) running on the client machine will receive a request to generate a quote for the application enclave. &amp;nbsp;At this point, the PSW detects whether EPID provisioning has occurred and if not, triggers the EPID provisioning process.&lt;/P&gt;

&lt;P&gt;In summary, the SGX PSW is responsible for EPID provisioning which is triggered as a result of the 1st attestation on that platform.&lt;/P&gt;</description>
    <pubDate>Mon, 18 Apr 2016 13:05:45 GMT</pubDate>
    <dc:creator>Derek_B_Intel</dc:creator>
    <dc:date>2016-04-18T13:05:45Z</dc:date>
    <item>
      <title>Initial SGX provisioning</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Initial-SGX-provisioning/m-p/1093582#M908</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;1. &lt;GS class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="a612e411-3910-401a-86f8-83f03c3169e9" id="b032f802-f7da-4e7d-a276-5cdfc72fcf54"&gt;Do&lt;/GS&gt; all SGX-platforms come pre-provisioned with an attestation key?&lt;/P&gt;

&lt;P&gt;2. Is provisioning an OEM's responsibility?&lt;/P&gt;

&lt;P&gt;3. In case the platform has not been provisioned, the attestation key is lost or in case the attestation key is out of date, How can I conduct the provisioning process to obtain a fresh EPID private key?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2016 08:42:38 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Initial-SGX-provisioning/m-p/1093582#M908</guid>
      <dc:creator>Alon_J_</dc:creator>
      <dc:date>2016-04-18T08:42:38Z</dc:date>
    </item>
    <item>
      <title>SGX platforms are not pre</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Initial-SGX-provisioning/m-p/1093583#M909</link>
      <description>&lt;P&gt;SGX platforms are not pre-provisioned.&lt;/P&gt;

&lt;P&gt;Provisioning is triggered as part of the attestation process. &amp;nbsp;When a SGX client application connects to the application server for the first time, the application server will trigger a challenge to the client to attest (running on a valid SGX client machine as well as verifying the validity of enclave running on the client).&lt;/P&gt;

&lt;P&gt;The SGX Platform Software (PSW) running on the client machine will receive a request to generate a quote for the application enclave. &amp;nbsp;At this point, the PSW detects whether EPID provisioning has occurred and if not, triggers the EPID provisioning process.&lt;/P&gt;

&lt;P&gt;In summary, the SGX PSW is responsible for EPID provisioning which is triggered as a result of the 1st attestation on that platform.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2016 13:05:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Initial-SGX-provisioning/m-p/1093583#M909</guid>
      <dc:creator>Derek_B_Intel</dc:creator>
      <dc:date>2016-04-18T13:05:45Z</dc:date>
    </item>
  </channel>
</rss>

