<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[wolfSSL - Embedded SSL Library — NetSecure_BlkGet - Where is this?]]></title>
		<link>https://www.wolfssl.com/forums/topic591-netsecureblkget-where-is-this.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic591.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in NetSecure_BlkGet - Where is this?.]]></description>
		<lastBuildDate>Fri, 31 Oct 2014 20:30:46 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: NetSecure_BlkGet - Where is this?]]></title>
			<link>https://www.wolfssl.com/forums/post1809.html#p1809</link>
			<description><![CDATA[<p>Where is your example server?</p>]]></description>
			<author><![CDATA[null@example.com (kbhave)]]></author>
			<pubDate>Fri, 31 Oct 2014 20:30:46 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post1809.html#p1809</guid>
		</item>
		<item>
			<title><![CDATA[Re: NetSecure_BlkGet - Where is this?]]></title>
			<link>https://www.wolfssl.com/forums/post1806.html#p1806</link>
			<description><![CDATA[<p>Hi,</p><p>Are you using Micrium&#039;s uC-OS?&nbsp; If not, can you find where NET_SECURE_MGR_CFG_EN is getting defined?&nbsp; I just want to make sure you&#039;re using the correct XMALLOC for your environment.</p><p>As I noted above, sometimes Google&#039;s certificates can be very large.&nbsp; Have you tried connecting to the wolfSSL example server which comes with the wolfSSL package?</p><p>Best Regards,<br />Chris</p>]]></description>
			<author><![CDATA[null@example.com (chrisc)]]></author>
			<pubDate>Thu, 30 Oct 2014 21:59:16 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post1806.html#p1806</guid>
		</item>
		<item>
			<title><![CDATA[Re: NetSecure_BlkGet - Where is this?]]></title>
			<link>https://www.wolfssl.com/forums/post1798.html#p1798</link>
			<description><![CDATA[<p>Any updates on this? Or any other pointers?</p>]]></description>
			<author><![CDATA[null@example.com (kbhave)]]></author>
			<pubDate>Wed, 29 Oct 2014 01:58:33 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post1798.html#p1798</guid>
		</item>
		<item>
			<title><![CDATA[Re: NetSecure_BlkGet - Where is this?]]></title>
			<link>https://www.wolfssl.com/forums/post1791.html#p1791</link>
			<description><![CDATA[<p>Okay. I tried using this Extension by adding the following 2 defines in settings.h :</p><div class="codebox"><pre><code>    #define HAVE_TLS_EXTENSIONS
    #define HAVE_MAX_FRAGMENT</code></pre></div><p>and in main.cpp where SSL is getting initialized,</p><div class="codebox"><pre><code>ssl = CyaSSL_new(ctx);
if (CyaSSL_CTX_UseMaxFragment(ctx, CYASSL_MFL_2_9) != SSL_SUCCESS) {
        printf(&quot;CyaSSL_CTX_UseMaxFragment failed\n&quot;);
        int  err = CyaSSL_get_error(ssl, 0);
        err_sys(&quot;SSL Connection Error&quot;);
    }</code></pre></div><p>Unfortunately, this did not have any effect and the program stopped at the same location. And I am still not sure why it uses NetSecure_BlkGet.</p>]]></description>
			<author><![CDATA[null@example.com (kbhave)]]></author>
			<pubDate>Fri, 24 Oct 2014 19:14:56 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post1791.html#p1791</guid>
		</item>
		<item>
			<title><![CDATA[Re: NetSecure_BlkGet - Where is this?]]></title>
			<link>https://www.wolfssl.com/forums/post1779.html#p1779</link>
			<description><![CDATA[<p>Hi,<br />The way I found out which XMALLOC will be used, is by using the same ifdef statements that you have in settings.h. So this is not from a Search. Basically, I added the following code in integer.c just before the call to XMALLOC, to determine which XMALLOC will be used:</p><div class="codebox"><pre><code>#if defined(CYASSL_LEANPSK) &amp;&amp; !defined(XMALLOC_USER)
    CYASSL_MSG(&quot;KRB: mp_init_size: Define 1&quot;);
#endif
#if defined(XMALLOC_USER) &amp;&amp; defined(SSN_BUILDING_LIBYASSL)
    CYASSL_MSG(&quot;KRB: mp_init_size: Define 2&quot;);
#endif
#ifdef EBSNET
    CYASSL_MSG(&quot;KRB: mp_init_size: Define 3&quot;);
#endif
#ifdef CYASSL_SAFERTOS
    CYASSL_MSG(&quot;KRB: mp_init_size: Define 4&quot;);
#endif
#ifdef FREESCALE_MQX
    CYASSL_MSG(&quot;KRB: mp_init_size: Define 5&quot;);
#endif
#if (NET_SECURE_MGR_CFG_EN == DEF_ENABLED)
    CYASSL_MSG(&quot;KRB: mp_init_size: Define 6. Uses NetSecure_BlkGet&quot;);
#endif</code></pre></div><p>So even I am confused as to why it uses this.</p><p>I will definitely look into this Maximum Fragment Length Extension.</p><p>Thanks,<br />Kedar</p>]]></description>
			<author><![CDATA[null@example.com (kbhave)]]></author>
			<pubDate>Fri, 24 Oct 2014 03:24:14 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post1779.html#p1779</guid>
		</item>
		<item>
			<title><![CDATA[Re: NetSecure_BlkGet - Where is this?]]></title>
			<link>https://www.wolfssl.com/forums/post1776.html#p1776</link>
			<description><![CDATA[<p>Hi,</p><p>The code you specified above is specific to our Micrium uC/OS build, which I&#039;m guessing you&#039;re probably not using.&nbsp; Your IDE may have just found the wrong XMALLOC define when you searched for the macro being called.</p><p>But it does sounds like you are running out of memory if XMALLOC is failing.&nbsp; Sometimes the Google certs get fairly large (I&#039;ve seen up to 11kB for a single cert).&nbsp; If you are using the normal big integer math library, with 2048-bit RSA keys, expected stack usage should be around 7kB, with heap usage around 17kB.</p><p>In addition to those numbers, wolfSSL&#039;s I/O buffer can grow up to 16kB (on the heap).&nbsp; This I/O buffer starts at 1kB, then grows and shrinks as needed.&nbsp; The maximum SSL/TLS record size is defined as 16kB.&nbsp; You may be able to reduce this using the Maximum Fragment Length Extension, which let&#039;s you specify a smaller maximum record size to use.</p><p>We put out a blog post about the Maximum Fragment Length Extension a while back, which can be found here:<br /><a href="http://www.yassl.com/yaSSL/Blog/Entries/2013/6/28_Using_Maximum_Fragment_Length_with_CyaSSL.html">http://www.yassl.com/yaSSL/Blog/Entries … yaSSL.html</a></p><p>API documentation for those functions can be found here:<br /><a href="http://www.yassl.com/yaSSL/Docs-cyassl-manual-17-13-cyassl-api-tls-extensions.html">http://www.yassl.com/yaSSL/Docs-cyassl- … sions.html</a></p><p>Best Regards,<br />Chris</p>]]></description>
			<author><![CDATA[null@example.com (chrisc)]]></author>
			<pubDate>Thu, 23 Oct 2014 23:07:13 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post1776.html#p1776</guid>
		</item>
		<item>
			<title><![CDATA[NetSecure_BlkGet - Where is this?]]></title>
			<link>https://www.wolfssl.com/forums/post1775.html#p1775</link>
			<description><![CDATA[<p>I am using a LPC1768 and while trying to establish SSL connection with Google, and using CyaSSL_CTX_set_verify(ctx, SSL_VERIFY_PEER, NULL), my program gets stuck in mp_init_size function (Integer.c) during Signature Verification. I traced this to a XMALLOC call. Looking at Settings.h and using standard debugging I see that it is using NetSecure_BlkGet -</p><p>#if (NET_SECURE_MGR_CFG_EN == DEF_ENABLED)<br />&nbsp; &nbsp; #define MICRIUM_MALLOC&nbsp; &nbsp; <br />&nbsp; &nbsp; #define XMALLOC(s, h, type) ((void *)NetSecure_BlkGet((CPU_INT08U)(type), \<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(CPU_SIZE_T)(s), (void *)0))</p><p>Now where is this NetSecure_BlkGet function and any idea why it gets stuck here?<br />Thanks.</p>]]></description>
			<author><![CDATA[null@example.com (kbhave)]]></author>
			<pubDate>Thu, 23 Oct 2014 21:07:04 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post1775.html#p1775</guid>
		</item>
	</channel>
</rss>
