<?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 HTTPS from within enclave in Intel Confidential Computing</title>
    <link>https://community.intel.com/t5/Intel-Confidential-Computing/HTTPS-from-within-enclave/m-p/1178361#M3451</link>
    <description>I was wondering whether its possible to establish a HTTPS connection from within an enclave, that does not require former remote attestation, without the use of ocalls? If so, is there example code available?</description>
    <pubDate>Fri, 29 Dec 2017 15:18:49 GMT</pubDate>
    <dc:creator>Marion_M_Intel</dc:creator>
    <dc:date>2017-12-29T15:18:49Z</dc:date>
    <item>
      <title>HTTPS from within enclave</title>
      <link>https://community.intel.com/t5/Intel-Confidential-Computing/HTTPS-from-within-enclave/m-p/1178361#M3451</link>
      <description>I was wondering whether its possible to establish a HTTPS connection from within an enclave, that does not require former remote attestation, without the use of ocalls? If so, is there example code available?</description>
      <pubDate>Fri, 29 Dec 2017 15:18:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Confidential-Computing/HTTPS-from-within-enclave/m-p/1178361#M3451</guid>
      <dc:creator>Marion_M_Intel</dc:creator>
      <dc:date>2017-12-29T15:18:49Z</dc:date>
    </item>
  </channel>
</rss>

