<?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 Memset-ing on enclaves  in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Memset-ing-on-enclaves/m-p/1162676#M2899</link>
    <description>&lt;P&gt;&lt;SPAN style="font-size: 1em; -webkit-text-size-adjust: 100%;"&gt;hi,&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;I noticed on a lot of sgx code examples that they explicitly memset allocated variables to 0 before leaving the trusted zone. Any insight on this? &amp;nbsp;Ithought enclaves' EPC is protected and doing memsets will reduce performance of applications.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Kind Regards,&lt;/P&gt;

&lt;P&gt;Elephant&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 24 Nov 2017 01:19:45 GMT</pubDate>
    <dc:creator>Elephant</dc:creator>
    <dc:date>2017-11-24T01:19:45Z</dc:date>
    <item>
      <title>Memset-ing on enclaves</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Memset-ing-on-enclaves/m-p/1162676#M2899</link>
      <description>&lt;P&gt;&lt;SPAN style="font-size: 1em; -webkit-text-size-adjust: 100%;"&gt;hi,&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;I noticed on a lot of sgx code examples that they explicitly memset allocated variables to 0 before leaving the trusted zone. Any insight on this? &amp;nbsp;Ithought enclaves' EPC is protected and doing memsets will reduce performance of applications.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Kind Regards,&lt;/P&gt;

&lt;P&gt;Elephant&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 01:19:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Memset-ing-on-enclaves/m-p/1162676#M2899</guid>
      <dc:creator>Elephant</dc:creator>
      <dc:date>2017-11-24T01:19:45Z</dc:date>
    </item>
    <item>
      <title>The reason of using memset is</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Memset-ing-on-enclaves/m-p/1162677#M2900</link>
      <description>&lt;P&gt;The reason of using memset is documented in the SGX Developer Guide at&amp;nbsp;&lt;A href="https://download.01.org/intel-sgx/linux-1.9/docs/Intel_SGX_Developer_Guide.pdf"&gt;https://download.01.org/intel-sgx/linux-1.9/docs/Intel_SGX_Developer_Guide.pdf&lt;/A&gt;&amp;nbsp;under the section of "Disposal of Enclave Secrets".&lt;/P&gt;

&lt;P&gt;Here is an excerpt:&amp;nbsp;"The enclave writer must use the memset_s() function to clear any variable that contained secret data. The use of this function guarantees that the compiler will not optimize away the write to memory intended by this function call and thus ensuring the secret data is cleared. Using memset_s() is especially important when secret data is stored in a dynamically allocated buffer"&lt;/P&gt;</description>
      <pubDate>Tue, 12 Dec 2017 08:43:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Memset-ing-on-enclaves/m-p/1162677#M2900</guid>
      <dc:creator>Hoang_N_Intel</dc:creator>
      <dc:date>2017-12-12T08:43:09Z</dc:date>
    </item>
  </channel>
</rss>

