<?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 Hello. in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/About-Sealing/m-p/1160207#M2834</link>
    <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;It really depends on the usage.&amp;nbsp; In simplest terms, the sgx_seal_data function requests via EGETKEY the processor seal key to encrypt the data, which is processor specific.&amp;nbsp; This means you would only be able to decrypt the data on that exact processor.&amp;nbsp; The sgx_aes_ctr_encrypt function takes the key to encrypt with as an input parameter, which could be the seal key if you wanted, or some other derived key.&amp;nbsp; Both functions ultimately encrypt with a 128bit AES key.&amp;nbsp; Also be aware that sgx_seal_data ultimately uses AES GCM and sgx_aes_ctr_encrypt uses AES CTR (of course, per the name), if that matters to your work.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
    <pubDate>Fri, 03 Jan 2020 16:31:18 GMT</pubDate>
    <dc:creator>Scott_R_Intel</dc:creator>
    <dc:date>2020-01-03T16:31:18Z</dc:date>
    <item>
      <title>About Sealing</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/About-Sealing/m-p/1160206#M2833</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is there any difference between the sgx_aes_ctr_encrypt and sgx_seal_data?&lt;/P&gt;&lt;P&gt;Since they are both used to encrypt the data, and I have tested their performance. They show similar performance.&lt;/P&gt;&lt;P&gt;Is there any suggestion to choose which encrypt function when I need to encrypt data?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2019 02:43:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/About-Sealing/m-p/1160206#M2833</guid>
      <dc:creator>ffan01</dc:creator>
      <dc:date>2019-12-20T02:43:12Z</dc:date>
    </item>
    <item>
      <title>Hello.</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/About-Sealing/m-p/1160207#M2834</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;It really depends on the usage.&amp;nbsp; In simplest terms, the sgx_seal_data function requests via EGETKEY the processor seal key to encrypt the data, which is processor specific.&amp;nbsp; This means you would only be able to decrypt the data on that exact processor.&amp;nbsp; The sgx_aes_ctr_encrypt function takes the key to encrypt with as an input parameter, which could be the seal key if you wanted, or some other derived key.&amp;nbsp; Both functions ultimately encrypt with a 128bit AES key.&amp;nbsp; Also be aware that sgx_seal_data ultimately uses AES GCM and sgx_aes_ctr_encrypt uses AES CTR (of course, per the name), if that matters to your work.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jan 2020 16:31:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/About-Sealing/m-p/1160207#M2834</guid>
      <dc:creator>Scott_R_Intel</dc:creator>
      <dc:date>2020-01-03T16:31:18Z</dc:date>
    </item>
  </channel>
</rss>

