<?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 — Wolfssl error -188 while connectivity with ipv6]]></title>
		<link>https://www.wolfssl.com/forums/topic2070-wolfssl-error-188-while-connectivity-with-ipv6.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic2070.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Wolfssl error -188 while connectivity with ipv6.]]></description>
		<lastBuildDate>Thu, 04 Jan 2024 18:44:46 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Wolfssl error -188 while connectivity with ipv6]]></title>
			<link>https://www.wolfssl.com/forums/post7404.html#p7404</link>
			<description><![CDATA[<p>Hello Bilal,</p><p>Thanks for joining the wolfSSL Forums. The -188 error indicates that the client should load a CA cert that can be used to verify the server&#039;s cert during the handshake. As you found, you can skip this check, or use a verify callback.</p><p>The -112 error is commonly encountered when a memory alloc fails.</p><p>Could you please tell us a bit about your project? Please feel free to send an email to support@wolfssl.com if you&#039;d prefer a more private discussion.</p><p>Thanks,<br />Eric - wolfSSL Support</p>]]></description>
			<author><![CDATA[null@example.com (embhorn)]]></author>
			<pubDate>Thu, 04 Jan 2024 18:44:46 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post7404.html#p7404</guid>
		</item>
		<item>
			<title><![CDATA[Wolfssl error -188 while connectivity with ipv6]]></title>
			<link>https://www.wolfssl.com/forums/post7403.html#p7403</link>
			<description><![CDATA[<p>We are working on adding support of IPv6 to our embedded device the connection is established to ipv6 server with 80 port successfully. Now, while connecting with wolfssl with 443 port we are facing the error issue -188 &quot;ASN no signer to confirm failure&quot;<br /><strong><br />We have also implemented the following step from readme file </strong><br />&quot;Note 2)<br />wolfSSL takes a different approach to certificate verification than OpenSSL does. The default policy for the client is to verify the server, this means that if you don&#039;t load CAs to verify the server you&#039;ll get a connect error, no signer error to confirm failure (-188).</p><p>If you want to mimic OpenSSL behavior of having SSL_connect succeed even if verifying the server fails and reducing security you can do this by calling:</p><p> wolfSSL_CTX_set_verify(ctx, SSL_VERIFY_NONE, 0);&quot;</p><p>After adding this command we are getting the error -112 &quot;mp_exptmod error state&quot;</p><p><strong>The communication logs are:</strong><br />00000.000 fdOpenSession: OOM<br />Service Status: DHCPC&nbsp; &nbsp; : Enabled&nbsp; :&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 000<br />wolfSSL_Init<br />wolfSSL_CTX_new_ex<br />wolfSSL_CertManagerNew<br />wolfSSL_CTX_load_verify_buffer_ex<br />Adding a CA<br />&nbsp; &nbsp; Parsed new CA<br />&nbsp; &nbsp; Freeing Parsed CA<br />&nbsp; &nbsp; Freeing der CA<br />&nbsp; &nbsp; &nbsp; &nbsp; OK Freeing der CA<br />Service Status: HTTP&nbsp; &nbsp; &nbsp;: Enabled&nbsp; :&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 000<br />wolfSSL_CTX_use_certificate_buffer<br />wolfSSL_CTX_use_PrivateKey_buffer<br />wolfSSL_CTX_use_certificate_buffer<br />Checking cert signature type<br />Not ECDSA cert signature<br />wolfSSL_CTX_use_PrivateKey_buffer<br />Service Status: DHCPC&nbsp; &nbsp; : Enabled&nbsp; : Running&nbsp; : 000<br />Validity Passed <br />Address: fe80::20e:fff:fe0b:0 on device 1 is UNIQUE<br />Address: 2404:3100:189d:67:20e:fff:fe0b: on device 1 is UNIQUE<br />Network Added: If-1:192.168.1.102<br />Service Status: DHCPC&nbsp; &nbsp; : Enabled&nbsp; : Running&nbsp; : 017</p><p>wolfSSL_CTX_new_ex<br />wolfSSL_CertManagerNew<br />wolfSSL_CTX_load_verify_buffer_ex<br />Adding a CA<br />&nbsp; &nbsp; Parsed new CA<br />&nbsp; &nbsp; Freeing Parsed CA<br />&nbsp; &nbsp; Freeing der CA<br />&nbsp; &nbsp; &nbsp; &nbsp; OK Freeing der CA<br />SSL_new<br />SSL_set_fd<br />SSL_set_read_fd<br />SSL_set_write_fd<br />SSL_free</p><p>Connection established Successfully<br />SSL_new<br />SSL_set_fd<br />SSL_set_read_fd<br />SSL_set_write_fd<br />wolfSSL_send()<br />SSL_write()<br />wolfSSL_negotiate<br />SSL_connect()<br />connect state: CLIENT_HELLO_SENT</p><p>-188<br />SSL_get_error<br />SSL_free<br />SSL_new<br />SSL_set_fd<br />SSL_set_read_fd<br />SSL_set_write_fd<br />wolfSSL_send()<br />SSL_write()<br />wolfSSL_negotiate<br />SSL_connect()<br />connect state: CLIENT_HELLO_SENT</p><br /><p><strong>Please guide us if there is anything we are missing? I have also added the logs.</strong>.</p>]]></description>
			<author><![CDATA[null@example.com (bilal.anwar)]]></author>
			<pubDate>Thu, 04 Jan 2024 17:25:43 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post7403.html#p7403</guid>
		</item>
	</channel>
</rss>
