<?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 Re:[eHSM-KMS] How is the remote attestation realized? in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1546671#M6028</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;generally, attestation is the process of demonstrating that a software executable has been properly instantiated on a platform that allows a remote party to gain confidence that the intended software is securely running within an enclave on a fully patched, Intel SGX enabled platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This&amp;nbsp;&lt;A href="https://github.com/intel/ehsm/tree/main" rel="noopener noreferrer" target="_blank"&gt;GitHub page&lt;/A&gt;&amp;nbsp;has explanation of an End-to-End Distributed and Scalable Cloud KMS (Key Management System) built on top of Intel SGX enclave-based HSM (Hardware Security Module), aka eHSM. This might help to answer your question.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Cordially,&lt;/P&gt;&lt;P&gt;Iffa&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 23 Nov 2023 01:11:46 GMT</pubDate>
    <dc:creator>Iffa_Intel</dc:creator>
    <dc:date>2023-11-23T01:11:46Z</dc:date>
    <item>
      <title>[eHSM-KMS] How is the remote attestation realized?</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1545983#M6023</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I am developing a system using eHSM-KMS.&lt;/P&gt;&lt;P&gt;&amp;nbsp; In the process, I am currently having trouble understanding how the remote attestation works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I have added logs to the eHSM-KMS source code to investigate remote attestation,&lt;BR /&gt;&amp;nbsp; The only thing I could figure out is that it is using SSL communication between DkeyServer and DkeyCache using OpenSSH.&lt;/P&gt;&lt;P&gt;&amp;nbsp; We also could only find that the self-certification function (tee_get_certificate_with_evidence) generated an error (SGX_OL_NETWORK_ERROR:0xe019) when the PCCS server did not exist.&lt;/P&gt;&lt;P&gt;&amp;nbsp; What kind of communication is going on between PCCServer, DkeyServer and DkeyCache?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; What I would like to know is as follows.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;When does eHSM-KMS communicate with the PCCS server?&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;What is passed when communicating with the PCCServer and what is obtained as a result?&lt;BR /&gt;　　&lt;BR /&gt;　Regards,.&lt;BR /&gt;　T_Tsuga&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 11:54:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1545983#M6023</guid>
      <dc:creator>T_Tsuga</dc:creator>
      <dc:date>2023-11-21T11:54:44Z</dc:date>
    </item>
    <item>
      <title>Re:[eHSM-KMS] How is the remote attestation realized?</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1546671#M6028</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;generally, attestation is the process of demonstrating that a software executable has been properly instantiated on a platform that allows a remote party to gain confidence that the intended software is securely running within an enclave on a fully patched, Intel SGX enabled platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This&amp;nbsp;&lt;A href="https://github.com/intel/ehsm/tree/main" rel="noopener noreferrer" target="_blank"&gt;GitHub page&lt;/A&gt;&amp;nbsp;has explanation of an End-to-End Distributed and Scalable Cloud KMS (Key Management System) built on top of Intel SGX enclave-based HSM (Hardware Security Module), aka eHSM. This might help to answer your question.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Cordially,&lt;/P&gt;&lt;P&gt;Iffa&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 23 Nov 2023 01:11:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1546671#M6028</guid>
      <dc:creator>Iffa_Intel</dc:creator>
      <dc:date>2023-11-23T01:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: Re:[eHSM-KMS] How is the remote attestation realized?</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1547045#M6031</link>
      <description>&lt;P&gt;Hello Iffa_Intel,&lt;BR /&gt;　&lt;BR /&gt;　Thank you for your answer.&lt;BR /&gt;　I checked the site you mentioned.&lt;BR /&gt;　I understood that this is also a product of Intel Corporation.&lt;BR /&gt;　I would like to ask some questions about this eHSM-KMS.&lt;BR /&gt;　If you know, please let me know if there is an appropriate contact for this.&lt;BR /&gt;　　&lt;BR /&gt;Regards, T_Tsuga&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2023 05:32:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1547045#M6031</guid>
      <dc:creator>T_Tsuga</dc:creator>
      <dc:date>2023-11-24T05:32:13Z</dc:date>
    </item>
    <item>
      <title>Re:[eHSM-KMS] How is the remote attestation realized?</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1548096#M6038</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;While EHSM is an Intel product, the support team on the EHSM Github is the appropriate contact to answer your questions. You can open a Github Issues thread here:&amp;nbsp;&lt;A href="https://github.com/intel/ehsm/issues" rel="noopener noreferrer" target="_blank"&gt;https://github.com/intel/ehsm/issues&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Cordially,&lt;/P&gt;&lt;P&gt;Iffa&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Nov 2023 01:02:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1548096#M6038</guid>
      <dc:creator>Iffa_Intel</dc:creator>
      <dc:date>2023-11-28T01:02:18Z</dc:date>
    </item>
    <item>
      <title>Re:[eHSM-KMS] How is the remote attestation realized?</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1549424#M6052</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 11pt;"&gt;Intel will no longer monitor this thread since we have provided a solution.&amp;nbsp;If you need any additional information from Intel, please submit a new question.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 11pt;"&gt;Cordially,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Calibri, sans-serif; font-size: 11pt;"&gt;Iffa&lt;/SPAN&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 01 Dec 2023 00:20:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/eHSM-KMS-How-is-the-remote-attestation-realized/m-p/1549424#M6052</guid>
      <dc:creator>Iffa_Intel</dc:creator>
      <dc:date>2023-12-01T00:20:47Z</dc:date>
    </item>
  </channel>
</rss>

