<?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 Remote Attestation Process - problem with IAS response in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Remote-Attestation-Process-problem-with-IAS-response/m-p/1109105#M1249</link>
    <description>&lt;DIV style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"&gt;
	&lt;DIV style=""&gt;
		&lt;DIV style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"&gt;
			&lt;DIV style=""&gt;Hello.&lt;/DIV&gt;

			&lt;P&gt;I am doing the process of remote attestation in a nodejs application. When I try to do a post to IAS, I receive this error:&lt;/P&gt;

			&lt;DIV style=""&gt;error: { Error: Parse Error&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.socketOnData (_http_client.js:411:20)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at emitOne (events.js:96:13)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.emit (events.js:191:7)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at readableAddChunk (_stream_readable.js:178:18)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.Readable.push (_stream_readable.js:136:10)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSWrap.onread (net.js:559:20) bytesParsed: 195, code: 'HPE_UNEXPECTED_CONTENT_LENGTH' }&lt;/DIV&gt;
			&amp;nbsp;

			&lt;DIV style=""&gt;Searching about this problem, I found out that this is related to a malformed response from IAS, as stated in:&lt;BR style="" /&gt;
				-&lt;SPAN class="Object" id="OBJ_PREFIX_DWT181_com_zimbra_url" role="link"&gt;&lt;A href="http://stackoverflow.com/questions/35525715/http-get-parse-error-code-hpe-unexpected-content-length" target="_blank"&gt;http://stackoverflow.com/questions/35525715/http-get-parse-error-code-hpe-unexpected-content-length&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;

			&lt;DIV style=""&gt;-&lt;SPAN class="Object" id="OBJ_PREFIX_DWT182_com_zimbra_url" role="link"&gt;&lt;A href="https://github.com/nodejs/node/issues/5754" target="_blank"&gt;https://github.com/nodejs/node/issues/5754&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;

			&lt;DIV style=""&gt;-&lt;SPAN class="Object" id="OBJ_PREFIX_DWT183_com_zimbra_url" role="link"&gt;&lt;A href="https://github.com/nodejs/node/issues/6517" target="_blank"&gt;https://github.com/nodejs/node/issues/6517&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
			&amp;nbsp;

			&lt;DIV style=""&gt;Can anyone please explain me if this format of the response from IAS could be "fixed"?&lt;/DIV&gt;
			&amp;nbsp;

			&lt;DIV style=""&gt;Thank you.&lt;/DIV&gt;
		&lt;/DIV&gt;
	&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Wed, 17 May 2017 21:02:32 GMT</pubDate>
    <dc:creator>Dalton_V_</dc:creator>
    <dc:date>2017-05-17T21:02:32Z</dc:date>
    <item>
      <title>Remote Attestation Process - problem with IAS response</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Remote-Attestation-Process-problem-with-IAS-response/m-p/1109105#M1249</link>
      <description>&lt;DIV style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"&gt;
	&lt;DIV style=""&gt;
		&lt;DIV style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"&gt;
			&lt;DIV style=""&gt;Hello.&lt;/DIV&gt;

			&lt;P&gt;I am doing the process of remote attestation in a nodejs application. When I try to do a post to IAS, I receive this error:&lt;/P&gt;

			&lt;DIV style=""&gt;error: { Error: Parse Error&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.socketOnData (_http_client.js:411:20)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at emitOne (events.js:96:13)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.emit (events.js:191:7)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at readableAddChunk (_stream_readable.js:178:18)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSSocket.Readable.push (_stream_readable.js:136:10)&lt;BR style="" /&gt;
				&amp;nbsp;&amp;nbsp;&amp;nbsp; at TLSWrap.onread (net.js:559:20) bytesParsed: 195, code: 'HPE_UNEXPECTED_CONTENT_LENGTH' }&lt;/DIV&gt;
			&amp;nbsp;

			&lt;DIV style=""&gt;Searching about this problem, I found out that this is related to a malformed response from IAS, as stated in:&lt;BR style="" /&gt;
				-&lt;SPAN class="Object" id="OBJ_PREFIX_DWT181_com_zimbra_url" role="link"&gt;&lt;A href="http://stackoverflow.com/questions/35525715/http-get-parse-error-code-hpe-unexpected-content-length" target="_blank"&gt;http://stackoverflow.com/questions/35525715/http-get-parse-error-code-hpe-unexpected-content-length&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;

			&lt;DIV style=""&gt;-&lt;SPAN class="Object" id="OBJ_PREFIX_DWT182_com_zimbra_url" role="link"&gt;&lt;A href="https://github.com/nodejs/node/issues/5754" target="_blank"&gt;https://github.com/nodejs/node/issues/5754&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;

			&lt;DIV style=""&gt;-&lt;SPAN class="Object" id="OBJ_PREFIX_DWT183_com_zimbra_url" role="link"&gt;&lt;A href="https://github.com/nodejs/node/issues/6517" target="_blank"&gt;https://github.com/nodejs/node/issues/6517&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
			&amp;nbsp;

			&lt;DIV style=""&gt;Can anyone please explain me if this format of the response from IAS could be "fixed"?&lt;/DIV&gt;
			&amp;nbsp;

			&lt;DIV style=""&gt;Thank you.&lt;/DIV&gt;
		&lt;/DIV&gt;
	&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 17 May 2017 21:02:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Remote-Attestation-Process-problem-with-IAS-response/m-p/1109105#M1249</guid>
      <dc:creator>Dalton_V_</dc:creator>
      <dc:date>2017-05-17T21:02:32Z</dc:date>
    </item>
  </channel>
</rss>

