<?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 IPPAESInit in Enclave  in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/IPPAESInit-in-Enclave/m-p/1157241#M2754</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am just wondering if IPPAESInit works the same way in the enclave (compiled with sgx_tcrypto) as with the traditional IPP library? I am using this function to initialize the context pointer in order to do AES-CBC encryption (using ippsAESEncryptCBC). Both Enclave and the client program share a key. It seems it is not working properly on the enclave side.&lt;/P&gt;

&lt;P&gt;I tried to print the content of the pCtx as an integer in both sides. On the client side (traditional IPP), it gives me a long integer (which is reasonable) and on the enclave it is giving me always 0. I am suspecting that it is not working properly.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;I tried to set the key again using &amp;nbsp;ippsAESSetKey, but pCtx (context)&amp;nbsp; is still giving 0.&lt;/P&gt;

&lt;P&gt;The project is compiled successfully and IPPAESInit is returning ippStsNoErr on both sides. This is a linux project.&lt;/P&gt;

&lt;P&gt;Thank you&lt;/P&gt;

&lt;P&gt;Maan&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 15 Nov 2017 09:25:04 GMT</pubDate>
    <dc:creator>Maan_Haj_Rachid</dc:creator>
    <dc:date>2017-11-15T09:25:04Z</dc:date>
    <item>
      <title>IPPAESInit in Enclave</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/IPPAESInit-in-Enclave/m-p/1157241#M2754</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am just wondering if IPPAESInit works the same way in the enclave (compiled with sgx_tcrypto) as with the traditional IPP library? I am using this function to initialize the context pointer in order to do AES-CBC encryption (using ippsAESEncryptCBC). Both Enclave and the client program share a key. It seems it is not working properly on the enclave side.&lt;/P&gt;

&lt;P&gt;I tried to print the content of the pCtx as an integer in both sides. On the client side (traditional IPP), it gives me a long integer (which is reasonable) and on the enclave it is giving me always 0. I am suspecting that it is not working properly.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;I tried to set the key again using &amp;nbsp;ippsAESSetKey, but pCtx (context)&amp;nbsp; is still giving 0.&lt;/P&gt;

&lt;P&gt;The project is compiled successfully and IPPAESInit is returning ippStsNoErr on both sides. This is a linux project.&lt;/P&gt;

&lt;P&gt;Thank you&lt;/P&gt;

&lt;P&gt;Maan&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2017 09:25:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/IPPAESInit-in-Enclave/m-p/1157241#M2754</guid>
      <dc:creator>Maan_Haj_Rachid</dc:creator>
      <dc:date>2017-11-15T09:25:04Z</dc:date>
    </item>
    <item>
      <title>There is nothing wrong with</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/IPPAESInit-in-Enclave/m-p/1157242#M2755</link>
      <description>&lt;P&gt;There is nothing wrong with the IPPAESInit function inside and outside the enclave. If you have a problem like mine, please make sure that you don't by accident, for any reason, change the encrypted buffer when passed to the enclave (like my situation). It is working fine.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2017 11:43:41 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/IPPAESInit-in-Enclave/m-p/1157242#M2755</guid>
      <dc:creator>Maan_Haj_Rachid</dc:creator>
      <dc:date>2017-11-21T11:43:41Z</dc:date>
    </item>
  </channel>
</rss>

