<?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 Syscalls are generally not in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/System-calls-inside-enclave/m-p/1140425#M2245</link>
    <description>&lt;P&gt;Syscalls are generally not allowed inside enclaves. If you're able to call one of them, it means that the SDK replaces this libc function with it's own implementation. In the SDK it's under tlibc.&lt;/P&gt;</description>
    <pubDate>Mon, 06 May 2019 22:08:14 GMT</pubDate>
    <dc:creator>Michalevsky__Yan</dc:creator>
    <dc:date>2019-05-06T22:08:14Z</dc:date>
    <item>
      <title>System calls inside enclave</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/System-calls-inside-enclave/m-p/1140424#M2244</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have observed that majority of the system calls, like fork() and rand() are prohibited inside the enclave. But, some of the memory based system calls, like mmap() are allowed.&lt;/P&gt;&lt;P&gt;Can anyone please explain why and how mmap() is allowed inside the enclaves?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2019 19:55:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/System-calls-inside-enclave/m-p/1140424#M2244</guid>
      <dc:creator>sharma__ramya</dc:creator>
      <dc:date>2019-05-06T19:55:44Z</dc:date>
    </item>
    <item>
      <title>Syscalls are generally not</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/System-calls-inside-enclave/m-p/1140425#M2245</link>
      <description>&lt;P&gt;Syscalls are generally not allowed inside enclaves. If you're able to call one of them, it means that the SDK replaces this libc function with it's own implementation. In the SDK it's under tlibc.&lt;/P&gt;</description>
      <pubDate>Mon, 06 May 2019 22:08:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/System-calls-inside-enclave/m-p/1140425#M2245</guid>
      <dc:creator>Michalevsky__Yan</dc:creator>
      <dc:date>2019-05-06T22:08:14Z</dc:date>
    </item>
  </channel>
</rss>

