<?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 Hi Adil, in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109441#M1262</link>
    <description>&lt;P&gt;Hi Adil,&lt;/P&gt;

&lt;P&gt;SGX seal keys are unique to the platform. Two different systems will not derive the same key from the same enclave.&lt;/P&gt;

&lt;P&gt;-Surenthar&lt;/P&gt;</description>
    <pubDate>Thu, 15 Dec 2016 03:03:36 GMT</pubDate>
    <dc:creator>Surenthar_S_Intel</dc:creator>
    <dc:date>2016-12-15T03:03:36Z</dc:date>
    <item>
      <title>Query about EGETKEY</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109437#M1258</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;As far as I understand, the EGETKEY command which is used to get a bunch of different keys uses some sort of hardware key to generate the sub-keys? Is that correct? If yes, are the hardware keys the same for each SGX machine or are they different per-machine?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Adil&lt;/P&gt;</description>
      <pubDate>Fri, 09 Dec 2016 08:19:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109437#M1258</guid>
      <dc:creator>AAhma10</dc:creator>
      <dc:date>2016-12-09T08:19:50Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109438#M1259</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;The Intel® SGX Architecture provides the hardware instructions,&amp;nbsp;&lt;SPAN style="font-size: 1em;"&gt;EREPORT and EGETKEY, to support attestation and sealing.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 1em;"&gt;The EREPORT instruction provides an evidence structure that is&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 1em;"&gt;cryptographically bound to the hardware for consumption by&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 1em;"&gt;attestation verifiers. EGETKEY provides enclave software with&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 1em;"&gt;access to the “Report” and “Seal” keys used in the attestation&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 1em;"&gt;and sealing process. EGETKEY provides access to persistent&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 1em;"&gt;Sealing Keys that enclave software can use to encrypt and&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 1em;"&gt;integrity-protect data.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;When invoking EGETKEY, the enclave selects criteria, or a policy, for which enclaves may access this sealing key. These policies are useful for controlling the accessibility of sensitive data to future versions of the enclave.&lt;/P&gt;

&lt;P&gt;Intel® SGX supports two policies for Seal Keys:&lt;BR /&gt;
	Sealing to the Enclave Identity&lt;BR /&gt;
	Sealing to the Sealing Identity&lt;/P&gt;

&lt;P&gt;Please refer the below link for more information&lt;/P&gt;

&lt;UL&gt;
	&lt;LI&gt;Introduction to Intel® SGX Sealing - &lt;A href="https://software.intel.com/en-us/blogs/2016/05/04/introduction-to-intel-sgx-sealing"&gt;https://software.intel.com/en-us/blogs/2016/05/04/introduction-to-intel-sgx-sealing&lt;/A&gt;&lt;/LI&gt;
	&lt;LI&gt;Innovative Technology for CPU Based Attestation and Sealing (4.SEALING) -&amp;nbsp;&lt;A href="https://software.intel.com/en-us/articles/innovative-technology-for-cpu-based-attestation-and-sealing"&gt;https://software.intel.com/en-us/articles/innovative-technology-for-cpu-based-attestation-and-sealing&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;-Surenthar&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2016 04:55:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109438#M1259</guid>
      <dc:creator>Surenthar_S_Intel</dc:creator>
      <dc:date>2016-12-12T04:55:49Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109439#M1260</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Thanks for the answer. Sorry if my question was unclear but I was wondering if one could get the same SGX seal key per different enclaves running on different SGX machines? I know that EGETKEY uses a hardware key to create its seal key alongwith either enclave information or signer's key. But is that hardware key different per machine or the same which could essentially mean that we can theoretically get the same key if we run the same enclave on different machines.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Adil&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2016 06:26:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109439#M1260</guid>
      <dc:creator>AAhma10</dc:creator>
      <dc:date>2016-12-13T06:26:02Z</dc:date>
    </item>
    <item>
      <title>Hi Adil,</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109440#M1261</link>
      <description>&lt;P&gt;Hi Adil,&lt;/P&gt;

&lt;P&gt;AFAIK, all keys are device independent, i.e. on different machine(CPU) the same enclave will get different keys using EGETKEY.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2016 08:40:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109440#M1261</guid>
      <dc:creator>Huorong_L_</dc:creator>
      <dc:date>2016-12-13T08:40:14Z</dc:date>
    </item>
    <item>
      <title>Hi Adil,</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109441#M1262</link>
      <description>&lt;P&gt;Hi Adil,&lt;/P&gt;

&lt;P&gt;SGX seal keys are unique to the platform. Two different systems will not derive the same key from the same enclave.&lt;/P&gt;

&lt;P&gt;-Surenthar&lt;/P&gt;</description>
      <pubDate>Thu, 15 Dec 2016 03:03:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109441#M1262</guid>
      <dc:creator>Surenthar_S_Intel</dc:creator>
      <dc:date>2016-12-15T03:03:36Z</dc:date>
    </item>
    <item>
      <title>Okay, that answers my</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109442#M1263</link>
      <description>&lt;P&gt;Okay, that answers my question. Thanks a lot for the replies!&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 1em;"&gt;Adil&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Dec 2016 03:48:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109442#M1263</guid>
      <dc:creator>AAhma10</dc:creator>
      <dc:date>2016-12-15T03:48:45Z</dc:date>
    </item>
    <item>
      <title>Hi @selvaraj,</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109443#M1264</link>
      <description>&lt;P&gt;Hi&amp;nbsp;@selvaraj,&lt;/P&gt;&lt;P&gt;While sgx_create_report, which key is used to generated sgx_msc_t (CMAC value of report data) ?&lt;/P&gt;&lt;P&gt;How QE(Quoting Enclave) Verifies the CMAC value!?&lt;/P&gt;&lt;P&gt;Is that key accessible to both app enclave and QE?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Aug 2019 11:02:57 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Query-about-EGETKEY/m-p/1109443#M1264</guid>
      <dc:creator>Anandakumar</dc:creator>
      <dc:date>2019-08-08T11:02:57Z</dc:date>
    </item>
  </channel>
</rss>

