<?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 Thanks Surenthar in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/SGX-enclaves/m-p/1069311#M259</link>
    <description>&lt;P&gt;Thanks Surenthar&lt;/P&gt;</description>
    <pubDate>Mon, 25 Jul 2016 04:37:17 GMT</pubDate>
    <dc:creator>Sam5</dc:creator>
    <dc:date>2016-07-25T04:37:17Z</dc:date>
    <item>
      <title>SGX enclaves</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/SGX-enclaves/m-p/1069309#M257</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Are there any guarantees for freshness of sealed data? In other words, rollback attack, where a malicious OS tries to roll the state of the enclave back to some earlier point in time: e.g., checkpoint the saved state, run the enclave for a while, then possibly restore back to the checkpoint. Can SGX code defend against such rollback attacks? If so, how?&lt;/P&gt;

&lt;P&gt;-Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 03:21:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/SGX-enclaves/m-p/1069309#M257</guid>
      <dc:creator>Sam5</dc:creator>
      <dc:date>2016-07-22T03:21:50Z</dc:date>
    </item>
    <item>
      <title>Hi Sam,</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/SGX-enclaves/m-p/1069310#M258</link>
      <description>&lt;P&gt;Hi Sam,&lt;/P&gt;

&lt;P&gt;The CPU does not directly provide such protection, but you can rely on the monotonic counter and the trusted time features of the ME to achieve it. They can be used to limit the duration for which a secret is valid (trusted time) and prevent replay attacks (monotonic counter). I would point them at the developer reference:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://community.intel.com/legacyfs/online/drupal_files/managed/b4/cf/Intel-SGX-SDK-Developer-Reference-for-Windows-OS.pdf"&gt;https://software.intel.com/sites/default/files/managed/b4/cf/Intel-SGX-SDK-Developer-Reference-for-Windows-OS.pdf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The section on Sealed Data talks about setting replay and time-based policies, and which functions in the SDK are there to assist.&lt;/P&gt;

&lt;P&gt;Thanks and Reagrds,&lt;BR /&gt;
	Surenthar Selvaraj&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2016 03:55:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/SGX-enclaves/m-p/1069310#M258</guid>
      <dc:creator>Surenthar_S_Intel</dc:creator>
      <dc:date>2016-07-25T03:55:40Z</dc:date>
    </item>
    <item>
      <title>Thanks Surenthar</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/SGX-enclaves/m-p/1069311#M259</link>
      <description>&lt;P&gt;Thanks Surenthar&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2016 04:37:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/SGX-enclaves/m-p/1069311#M259</guid>
      <dc:creator>Sam5</dc:creator>
      <dc:date>2016-07-25T04:37:17Z</dc:date>
    </item>
  </channel>
</rss>

