<?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 — Server on embedded device]]></title>
		<link>https://www.wolfssl.com/forums/topic1818-server-on-embedded-device.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic1818.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Server on embedded device.]]></description>
		<lastBuildDate>Thu, 18 Nov 2021 19:49:01 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6375.html#p6375</link>
			<description><![CDATA[<p>Hi Alex,</p><p>You will want to use SP math rather than Fast math to increase your speed.&nbsp; Replace USE_FAST_MATH with the following:<br />WOLFSSL_SP_MATH_ALL<br />WOLFSSL_SP_ASM<br />Let me know if you still have speed issues.</p><p>Thanks,<br />Kareem</p>]]></description>
			<author><![CDATA[null@example.com (kareem_wolfssl)]]></author>
			<pubDate>Thu, 18 Nov 2021 19:49:01 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6375.html#p6375</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6370.html#p6370</link>
			<description><![CDATA[<p>Hi Kareem,</p><p>Any idea why removing GCM_SMALL define did not have any impact on speed? Anything else should be removed?</p><p>Currently my defines look like this:</p><p>CUSTOM_RAND_GENERATE_SEED<br />NO_WRITEV<br />NO_WOLFSSL_DIR<br />TFM_TIMING_RESISTANT<br />ECC_TIMING_RESISTANT<br />WC_RSA_BLINDING<br />HAVE_AESCCM<br />HAVE_AESGCM<br />HAVE_ECC<br />HAVE_AES_CBC<br />WOLFSSL_AES_128<br />WOLFSSL_AES_256 <br />ECC_USER_CURVES <br />HAVE_HKDF<br />HAVE_FFDHE_2048 <br />WC_RSA_PSS<br />WOLFSSL_ENCRYPTED_KEYS<br />HAVE_TLS_EXTENSIONS<br />HAVE_SUPPORTED_CURVES<br />WOLFSSL_SHA384<br />WOLFSSL_SHA512<br />WOLFSSL_TLS13<br />USE_FAST_MATH<br />ALT_ECC_SIZE</p><p>Regards,</p><p>Alex</p>]]></description>
			<author><![CDATA[null@example.com (alex2021)]]></author>
			<pubDate>Wed, 17 Nov 2021 21:24:53 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6370.html#p6370</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6369.html#p6369</link>
			<description><![CDATA[<p>Hi Alex,</p><p>If your platform doesn&#039;t support hardware acceleration for AES, I would recommend trying Chacha/Poly.&nbsp; Yes, you should remove your fast math define.<br />You are correct that ARMASM won&#039;t work with ARMv5, but you should still be able to use SP math assembly which I would definitely recommend.</p><p>Thanks,<br />Kareem</p>]]></description>
			<author><![CDATA[null@example.com (kareem_wolfssl)]]></author>
			<pubDate>Wed, 17 Nov 2021 19:59:47 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6369.html#p6369</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6365.html#p6365</link>
			<description><![CDATA[<p>Hi Kareem,</p><p>I am working on armv5 chip, so WOLFSSL_ARMASM will not work for me I guess. I tried removing GCM_SMALL and it had no impact on the speed. What cipher suite would you recommend for faster processing speed? Also , to use SP math do in eed to remove fast math define?</p><p>Regards,</p><p>Alex</p>]]></description>
			<author><![CDATA[null@example.com (alex2021)]]></author>
			<pubDate>Wed, 17 Nov 2021 00:41:53 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6365.html#p6365</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6364.html#p6364</link>
			<description><![CDATA[<p>Hi Alex,</p><p>Glad to hear you were able to resolve your issue.&nbsp; What platform/architecture are you on?&nbsp; Which cipher suite are you using?<br />In general, I&#039;d recommend using SP math over fast math, and SP math assembly if your platform supports it.<br />Check out our user settings template here for more info on our SP math and other settings: <a href="https://github.com/wolfSSL/wolfssl/blob/master/examples/configs/user_settings_template.h">https://github.com/wolfSSL/wolfssl/blob … template.h</a><br />I would also enable ARM assembly with WOLFSSL_ARMASM, assuming you&#039;re on ARM.<br />You will want to disable small AES-GCM if possible as it will have a significant speed impact (GCM_SMALL).</p><p>Thanks,<br />Kareem</p>]]></description>
			<author><![CDATA[null@example.com (kareem_wolfssl)]]></author>
			<pubDate>Tue, 16 Nov 2021 21:17:01 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6364.html#p6364</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6363.html#p6363</link>
			<description><![CDATA[<p>Hi Kareem,</p><p>Switching to server TLS 1.3 from TLS 1.2 resolves the problem I had, but it makes processing each connection request 4 or 5 times longer. What is the best way to optimize for speed? Right now each request takes 2 seconds to process, which will create a jerky performance for users.</p><p>Regards,</p><p>Alex</p>]]></description>
			<author><![CDATA[null@example.com (alex2021)]]></author>
			<pubDate>Tue, 16 Nov 2021 20:46:32 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6363.html#p6363</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6360.html#p6360</link>
			<description><![CDATA[<p>Hi Kareem,</p><p>To answer your questions:</p><p><strong>What platform and OS are you using? </strong><br />I am using embedded RTOS<br /><strong>How much stack/heap are you giving to wolfSSL?</strong><br />I believe stack and heap should be sufficient since website is running normally after browser restart. Also during reboot all the wolfssl objects are released.<br /><strong>What kind of webpage are you serving with wolfSSL? </strong><br />It a webpage of user interface that constantly sending ajax requests and gets back some data.<br /><strong>Is it something that would spawn multiple connections?</strong><br />There could be several request pending, but not to much.<br /><strong>Does closing your Chrome tab and opening a new one resolve the issue, or does it require a full browser restart?</strong><br />Closing reopening tab is not working. Only full restart of the browser does.<br />It does seem like Chrome tries to connect to previous connection since netstat list many TIME_WAIT ports trying to connect to server after server is restarted once.</p><p>After first restart of the server the browser still connects to website however every second wolfssl_accept gives alert error as shown in previous posts. After second restart, browsers can&#039;t connect to website and just displays ssl_connection_error, while every wolfssl_accept throws an error.</p><p>Regards,</p><p>Alex</p>]]></description>
			<author><![CDATA[null@example.com (alex2021)]]></author>
			<pubDate>Thu, 11 Nov 2021 06:15:06 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6360.html#p6360</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6357.html#p6357</link>
			<description><![CDATA[<p>Hi Alex,</p><p>What platform and OS are you using?&nbsp; How much stack/heap are you giving to wolfSSL?<br />What kind of webpage are you serving with wolfSSL?&nbsp; Is it something that would spawn multiple connections?<br />Does closing your Chrome tab and opening a new one resolve the issue, or does it require a full browser restart?</p><p>If this information is too sensitive to share in a public forum, feel free to contact us at support@wolfssl.com</p><p>Thanks,<br />Kareem</p>]]></description>
			<author><![CDATA[null@example.com (kareem_wolfssl)]]></author>
			<pubDate>Wed, 10 Nov 2021 00:20:32 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6357.html#p6357</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6355.html#p6355</link>
			<description><![CDATA[<p>Hi Kareem,</p><p>After updating to 5.0, I still have the same problem. After rebooting a server once and not touching the browser following is the log of the error:</p><p>WOLFSSL MSG: wolfSSL Entering SSL_accept()<br />WOLFSSL MSG: Client attempting to connect with different version<br />WOLFSSL MSG: growing input buffer<br />WOLFSSL MSG: received record layer msg<br />WOLFSSL MSG: got HANDSHAKE<br />WOLFSSL MSG: wolfSSL Entering DoHandShakeMsg()<br />WOLFSSL MSG: wolfSSL Entering DoHandShakeMsgType<br />WOLFSSL MSG: processing client hello<br />WOLFSSL MSG: wolfSSL Entering DoClientHello<br />WOLFSSL MSG: Client wants to resume session<br />WOLFSSL MSG: Matched No Compression<br />WOLFSSL MSG: Adding signature algorithms extension<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Secure Renegotiation extension received<br />WOLFSSL MSG: Supported Groups extension received<br />WOLFSSL MSG: Point Formats extension received<br />WOLFSSL MSG: Session Ticket extension received<br />WOLFSSL MSG: ALPN extension received<br />WOLFSSL MSG: Certificate Status Request extension received<br />WOLFSSL MSG: Signature Algorithms extension received<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Key Share extension received<br />WOLFSSL MSG: PSK Key Exchange Modes extension received<br />WOLFSSL MSG: Skipping Supported Versions - already processed<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Found a session match<br />WOLFSSL MSG: Session valid<br />WOLFSSL MSG: wolfSSL Entering MatchSuite<br />WOLFSSL MSG: wolfSSL Entering VerifyServerSuite<br />WOLFSSL MSG: Requires RSA<br />WOLFSSL MSG: Requires AEAD<br />WOLFSSL MSG: Verified suite validity<br />WOLFSSL MSG: wolfSSL Leaving DoClientHello, return 0<br />WOLFSSL MSG: Shrinking input buffer<br />WOLFSSL MSG: wolfSSL Leaving DoHandShakeMsgType(), return 0<br />WOLFSSL MSG: wolfSSL Leaving DoHandShakeMsg(), return 0<br />WOLFSSL MSG: accept state ACCEPT_CLIENT_HELLO_DONE<br />WOLFSSL MSG: accept state ACCEPT_FIRST_REPLY_DONE<br />WOLFSSL MSG: wolfSSL Entering SendServerHello<br />WOLFSSL MSG: Point Formats extension to write<br />WOLFSSL MSG: wolfSSL Leaving SendServerHello, return 0<br />WOLFSSL MSG: accept state SERVER_HELLO_SENT<br />WOLFSSL MSG: accept state CERT_SENT<br />WOLFSSL MSG: accept state CERT_STATUS_SENT<br />WOLFSSL MSG: accept state KEY_EXCHANGE_SENT<br />WOLFSSL MSG: accept state CERT_REQ_SENT<br />WOLFSSL MSG: accept state SERVER_HELLO_DONE<br />WOLFSSL MSG: accept state&nbsp; ACCEPT_SECOND_REPLY_DONE<br />WOLFSSL MSG: accept state&nbsp; TICKET_SENT<br />WOLFSSL MSG: accept state&nbsp; CHANGE_CIPHER_SENT<br />WOLFSSL MSG: wolfSSL Entering SendFinished<br />WOLFSSL MSG: wolfSSL Leaving SendFinished, return 0<br />WOLFSSL MSG: accept state ACCEPT_FINISHED_DONE<br />WOLFSSL MSG: received record layer msg<br />WOLFSSL MSG: got ALERT!<br />WOLFSSL MSG: wolfSSL error occurred, error = -132<br />WOLFSSL MSG: wolfSSL Entering SSL_get_error<br />WOLFSSL MSG: wolfSSL Leaving SSL_get_error, return -132<br />WOLFSSL MSG: wolfSSL Entering SSL_get_error<br />WOLFSSL MSG: wolfSSL Leaving SSL_get_error, return -132<br />WOLFSSL MSG: wolfSSL Entering wolfSSL_ERR_error_string_n<br />WOLFSSL MSG: Error buffer too short, truncating<br />WOLFSSL MSG: wolfSSL Entering ERR_error_string<br />WOLFSSL MSG: wolfSSL Entering SSL_shutdown()<br />WOLFSSL MSG: wolfSSL Entering SendAlert<br />WOLFSSL MSG: Embed Send error<br />WOLFSSL MSG:&nbsp; &nbsp; Connection aborted<br />WOLFSSL MSG: wolfSSL Leaving SendAlert, return -308<br />WOLFSSL MSG: wolfSSL error occurred, error = -308<br />WOLFSSL MSG: wolfSSL Entering SSL_free<br />WOLFSSL MSG: CTX ref count not 0 yet, no free<br />WOLFSSL MSG: wolfSSL Leaving SSL_free, return 0<br />WOLFSSL MSG: wolfSSL Entering SSL_new<br />WOLFSSL MSG: wolfSSL Leaving SSL_new, return 0</p><br /><br /><p>After rebooting twice, I get the following behaviour:</p><p>WOLFSSL MSG: wolfSSL Entering SSL_accept()<br />WOLFSSL MSG: Client attempting to connect with different version<br />WOLFSSL MSG: growing input buffer<br />WOLFSSL MSG: received record layer msg<br />WOLFSSL MSG: got HANDSHAKE<br />WOLFSSL MSG: wolfSSL Entering DoHandShakeMsg()<br />WOLFSSL MSG: wolfSSL Entering DoHandShakeMsgType<br />WOLFSSL MSG: processing client hello<br />WOLFSSL MSG: wolfSSL Entering DoClientHello<br />WOLFSSL MSG: Client wants to resume session<br />WOLFSSL MSG: Matched No Compression<br />WOLFSSL MSG: Adding signature algorithms extension<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Secure Renegotiation extension received<br />WOLFSSL MSG: Supported Groups extension received<br />WOLFSSL MSG: Point Formats extension received<br />WOLFSSL MSG: Session Ticket extension received<br />WOLFSSL MSG: ALPN extension received<br />WOLFSSL MSG: Certificate Status Request extension received<br />WOLFSSL MSG: Signature Algorithms extension received<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Key Share extension received<br />WOLFSSL MSG: PSK Key Exchange Modes extension received<br />WOLFSSL MSG: Skipping Supported Versions - already processed<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Unknown TLS extension type<br />WOLFSSL MSG: Session lookup for resume failed<br />WOLFSSL MSG: wolfSSL Entering MatchSuite<br />WOLFSSL MSG: wolfSSL Entering VerifyServerSuite<br />WOLFSSL MSG: Requires RSA<br />WOLFSSL MSG: Requires AEAD<br />WOLFSSL MSG: Verified suite validity<br />WOLFSSL MSG: wolfSSL Leaving DoClientHello, return 0<br />WOLFSSL MSG: Shrinking input buffer<br />WOLFSSL MSG: wolfSSL Leaving DoHandShakeMsgType(), return 0<br />WOLFSSL MSG: wolfSSL Leaving DoHandShakeMsg(), return 0<br />WOLFSSL MSG: accept state ACCEPT_CLIENT_HELLO_DONE<br />WOLFSSL MSG: accept state ACCEPT_FIRST_REPLY_DONE<br />WOLFSSL MSG: wolfSSL Entering SendServerHello<br />WOLFSSL MSG: Point Formats extension to write<br />WOLFSSL MSG: wolfSSL Leaving SendServerHello, return 0<br />WOLFSSL MSG: accept state SERVER_HELLO_SENT<br />WOLFSSL MSG: wolfSSL Entering SendCertificate<br />WOLFSSL MSG: wolfSSL Leaving SendCertificate, return 0<br />WOLFSSL MSG: accept state CERT_SENT<br />WOLFSSL MSG: wolfSSL Entering SendCertificateStatus<br />WOLFSSL MSG: wolfSSL Leaving SendCertificateStatus, return 0<br />WOLFSSL MSG: accept state CERT_STATUS_SENT<br />WOLFSSL MSG: wolfSSL Entering SendServerKeyExchange<br />WOLFSSL MSG: Using ephemeral ECDH<br />WOLFSSL MSG: wolfSSL Entering EccMakeKey<br />WOLFSSL MSG: wolfSSL Leaving EccMakeKey, return 0<br />WOLFSSL MSG: Trying RSA private key<br />WOLFSSL MSG: wolfSSL Entering GetAlgoId<br />WOLFSSL MSG: wolfSSL Entering GetObjectId()<br />WOLFSSL MSG: Using RSA private key<br />WOLFSSL MSG: wolfSSL Entering RsaSign<br />WOLFSSL MSG: wolfSSL Using RSA PSS padding<br />WOLFSSL MSG: wolfSSL Leaving RsaSign, return 0<br />WOLFSSL MSG: wolfSSL Entering VerifyRsaSign<br />WOLFSSL MSG: wolfSSL Using RSA PSS un-padding<br />WOLFSSL MSG: wolfSSL Leaving VerifyRsaSign, return 0<br />WOLFSSL MSG: wolfSSL Entering SendHandshakeMsg<br />WOLFSSL MSG: Embed Send error<br />WOLFSSL MSG:&nbsp; &nbsp; Connection aborted<br />WOLFSSL MSG: wolfSSL Leaving SendServerKeyExchange, return -308<br />WOLFSSL MSG: wolfSSL error occurred, error = -308<br />WOLFSSL MSG: wolfSSL Entering SSL_get_error<br />WOLFSSL MSG: wolfSSL Leaving SSL_get_error, return -308<br />WOLFSSL MSG: wolfSSL Entering SSL_get_error<br />WOLFSSL MSG: wolfSSL Leaving SSL_get_error, return -308<br />WOLFSSL MSG: wolfSSL Entering wolfSSL_ERR_error_string_n<br />WOLFSSL MSG: Error buffer too short, truncating<br />WOLFSSL MSG: wolfSSL Entering ERR_error_string<br />WOLFSSL MSG: wolfSSL Entering SSL_shutdown()<br />WOLFSSL MSG: wolfSSL Leaving SSL_shutdown(), return -1<br />WOLFSSL MSG: wolfSSL Entering SSL_free<br />WOLFSSL MSG: CTX ref count not 0 yet, no free<br />WOLFSSL MSG: wolfSSL Leaving SSL_free, return 0<br />WOLFSSL MSG: wolfSSL Entering SSL_new<br />WOLFSSL MSG: wolfSSL Leaving SSL_new, return 0<br />WOLFSSL MSG: wolfSSL Entering SSL_set_fd<br />WOLFSSL MSG: wolfSSL Entering SSL_set_read_fd<br />WOLFSSL MSG: wolfSSL Leaving SSL_set_read_fd, return 1<br />WOLFSSL MSG: wolfSSL Entering SSL_set_write_fd<br />WOLFSSL MSG: wolfSSL Leaving SSL_set_write_fd, return 1</p><p>Regards,</p><p>Alex</p>]]></description>
			<author><![CDATA[null@example.com (alex2021)]]></author>
			<pubDate>Tue, 09 Nov 2021 21:32:40 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6355.html#p6355</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6351.html#p6351</link>
			<description><![CDATA[<p>Hi Alex,</p><p>3.15.3 is extremely outdated and unsupported.&nbsp; Please update to 5.0 and let me know if it fixes the issue for you.</p>]]></description>
			<author><![CDATA[null@example.com (kareem_wolfssl)]]></author>
			<pubDate>Fri, 05 Nov 2021 17:19:10 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6351.html#p6351</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6350.html#p6350</link>
			<description><![CDATA[<p>Hi Kareem,</p><p>To answer your questions:</p><p>1) hard refresh does not work<br />2) I am running version 3.15.3</p>]]></description>
			<author><![CDATA[null@example.com (alex2021)]]></author>
			<pubDate>Thu, 04 Nov 2021 21:57:06 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6350.html#p6350</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6349.html#p6349</link>
			<description><![CDATA[<p>Hi Alex,</p><p>A couple of questions:<br />1) Does a hard refresh (usually Ctrl+F5) show the same issue in your browser?<br />2) What version of wolfSSL are you using?&nbsp; Do you still see the issue with the latest wolfSSL, 5.0?</p><p>Thanks,<br />Kareem</p>]]></description>
			<author><![CDATA[null@example.com (kareem_wolfssl)]]></author>
			<pubDate>Thu, 04 Nov 2021 21:36:38 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6349.html#p6349</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6347.html#p6347</link>
			<description><![CDATA[<p>Hi Kareem,</p><p>Thank you for clarification. I am running wolfssl as a server and a client just a chrome browser.</p><p>My current problem is that any time I reset the server browser start failing to exhange certificate with the server resuilting in following sequence:</p><p>WOLFSSL MSG: wolfSSL Entering SSL_accept()<br />WOLFSSL MSG: Client attempting to connect with different version<br />WOLFSSL MSG: growing input buffer<br />WOLFSSL MSG: received record layer msg<br />WOLFSSL MSG: wolfSSL Entering DoHandShakeMsg()<br />WOLFSSL MSG: wolfSSL Entering DoHandShakeMsgType<br />WOLFSSL MSG: processing client hello<br />WOLFSSL MSG: wolfSSL Entering DoClientHello<br />WOLFSSL MSG: Client wants to resume session<br />WOLFSSL MSG: Matched No Compression<br />WOLFSSL MSG: Adding signature algorithms extension<br />WOLFSSL MSG: Secure Renegotiation extension received<br />WOLFSSL MSG: Supported Groups extension received<br />WOLFSSL MSG: Point Formats extension received<br />WOLFSSL MSG: Session Ticket extension received<br />WOLFSSL MSG: ALPN extension received<br />WOLFSSL MSG: Certificate Status Request extension received<br />WOLFSSL MSG: Signature Algorithms extension received<br />WOLFSSL MSG: Key Share extension received<br />WOLFSSL MSG: PSK Key Exchange Modes extension received<br />WOLFSSL MSG: Supported Versions extension received<br />WOLFSSL MSG: Session lookup for resume failed<br />WOLFSSL MSG: wolfSSL Entering MatchSuite<br />WOLFSSL MSG: wolfSSL Entering VerifyServerSuite<br />WOLFSSL MSG: Requires RSA<br />WOLFSSL MSG: Verified suite validity<br />WOLFSSL MSG: wolfSSL Leaving DoClientHello, return 0<br />WOLFSSL MSG: wolfSSL Leaving DoHandShakeMsgType(), return 0<br />WOLFSSL MSG: wolfSSL Leaving DoHandShakeMsg(), return 0<br />WOLFSSL MSG: accept state ACCEPT_CLIENT_HELLO_DONE<br />WOLFSSL MSG: accept state ACCEPT_FIRST_REPLY_DONE<br />WOLFSSL MSG: wolfSSL Entering SendServerHello<br />WOLFSSL MSG: Point Formats extension to write<br />WOLFSSL MSG: wolfSSL Leaving SendServerHello, return 0<br />WOLFSSL MSG: accept state SERVER_HELLO_SENT<br />WOLFSSL MSG: wolfSSL Entering SendCertificate<br />WOLFSSL MSG: wolfSSL Leaving SendCertificate, return 0<br />WOLFSSL MSG: accept state CERT_SENT<br />WOLFSSL MSG: wolfSSL Entering SendCertificateStatus<br />WOLFSSL MSG: wolfSSL Leaving SendCertificateStatus, return 0<br />WOLFSSL MSG: accept state CERT_STATUS_SENT<br />WOLFSSL MSG: wolfSSL Entering SendServerKeyExchange<br />WOLFSSL MSG: Using ephemeral ECDH<br />WOLFSSL MSG: wolfSSL Entering EccMakeKey<br />WOLFSSL MSG: wolfSSL Leaving EccMakeKey, return 0<br />WOLFSSL MSG: wolfSSL Entering RsaSign<br />WOLFSSL MSG: wolfSSL Using RSA PSS padding<br />WOLFSSL MSG: wolfSSL Leaving RsaSign, return 0<br />WOLFSSL MSG: wolfSSL Entering VerifyRsaSign<br />WOLFSSL MSG: wolfSSL Using RSA PSS un-padding<br />WOLFSSL MSG: wolfSSL Leaving VerifyRsaSign, return 0<br />WOLFSSL MSG: Embed Send error<br />WOLFSSL MSG:&nbsp; &nbsp; General error<br />WOLFSSL MSG: wolfSSL Leaving SendServerKeyExchange, return -5307<br />WOLFSSL MSG: wolfSSL error occurred, error = -5307<br />WOLFSSL MSG: wolfSSL Entering SSL_get_error</p><p>I do wolfssl_cleanup and free ctx object as well as close all listening sockets before reseting the server, but it seems the browser will not accept certificate after reset of the server, unless I close and reopen the browser.</p><p>Any ideas on how to force or notify browser that the old connection is closed? Or anything else I am missing?</p><p>Regards,</p><p>Alex</p>]]></description>
			<author><![CDATA[null@example.com (alex2021)]]></author>
			<pubDate>Thu, 04 Nov 2021 18:23:32 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6347.html#p6347</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6340.html#p6340</link>
			<description><![CDATA[<p>Hi Alex2021,</p><p>&quot;Client attempting to connect with different version&quot; means the client and server&#039;s TLS versions are not matching.&nbsp; What TLS version is your client using?<br />If for example your client is using TLS 1.0, you will need to define WOLFSSL_ALLOW_TLSV10.&nbsp; If your client is using TLS 1.2, it may help to undefine WOLFSSL_TLS13.</p><p>Thanks,<br />Kareem</p>]]></description>
			<author><![CDATA[null@example.com (kareem_wolfssl)]]></author>
			<pubDate>Mon, 01 Nov 2021 20:57:50 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6340.html#p6340</guid>
		</item>
		<item>
			<title><![CDATA[Re: Server on embedded device]]></title>
			<link>https://www.wolfssl.com/forums/post6339.html#p6339</link>
			<description><![CDATA[<p>I am still having issues with strange behaviour of the server. If reset my device, after restarting server recovers but every second accept results in Alert 20 bad_mac_err. If I restart it again it results in browser displayin ssl error until i restart the browser.</p><p>Here the debug messages I get:</p><p>WOLFSSL MSG: wolfSSL Entering SSL_accept()<br />WOLFSSL MSG: Client attempting to connect with different version<br />WOLFSSL MSG: growing input buffer<br />WOLFSSL MSG: received record layer msg<br />WOLFSSL MSG: wolfSSL Entering DoHandShakeMsg()<br />WOLFSSL MSG: wolfSSL Entering DoHandShakeMsgType<br />WOLFSSL MSG: processing client hello<br />WOLFSSL MSG: wolfSSL Entering DoClientHello<br />WOLFSSL MSG: Client wants to resume session<br />WOLFSSL MSG: Matched No Compression<br />WOLFSSL MSG: Adding signature algorithms extension<br />WOLFSSL MSG: Secure Renegotiation extension received<br />WOLFSSL MSG: Supported Groups extension received<br />WOLFSSL MSG: Point Formats extension received<br />WOLFSSL MSG: Session Ticket extension received<br />WOLFSSL MSG: ALPN extension received<br />WOLFSSL MSG: Certificate Status Request extension received<br />WOLFSSL MSG: Signature Algorithms extension received<br />WOLFSSL MSG: Key Share extension received<br />WOLFSSL MSG: PSK Key Exchange Modes extension received<br />WOLFSSL MSG: Supported Versions extension received<br />WOLFSSL MSG: Found a session match<br />WOLFSSL MSG: Session valid<br />WOLFSSL MSG: wolfSSL Entering MatchSuite<br />WOLFSSL MSG: wolfSSL Entering VerifyServerSuite<br />WOLFSSL MSG: Requires RSA<br />WOLFSSL MSG: Verified suite validity<br />WOLFSSL MSG: wolfSSL Leaving DoClientHello, return 0<br />WOLFSSL MSG: wolfSSL Leaving DoHandShakeMsgType(), return 0<br />WOLFSSL MSG: wolfSSL Leaving DoHandShakeMsg(), return 0<br />WOLFSSL MSG: accept state ACCEPT_CLIENT_HELLO_DONE<br />WOLFSSL MSG: accept state ACCEPT_FIRST_REPLY_DONE<br />WOLFSSL MSG: wolfSSL Entering SendServerHello<br />WOLFSSL MSG: Point Formats extension to write<br />WOLFSSL MSG: wolfSSL Leaving SendServerHello, return 0<br />WOLFSSL MSG: accept state SERVER_HELLO_SENT<br />WOLFSSL MSG: accept state CERT_SENT<br />WOLFSSL MSG: accept state CERT_STATUS_SENT<br />WOLFSSL MSG: accept state KEY_EXCHANGE_SENT<br />WOLFSSL MSG: accept state CERT_REQ_SENT<br />WOLFSSL MSG: accept state SERVER_HELLO_DONE<br />WOLFSSL MSG: accept state&nbsp; ACCEPT_SECOND_REPLY_DONE<br />WOLFSSL MSG: accept state&nbsp; TICKET_SENT<br />WOLFSSL MSG: accept state&nbsp; CHANGE_CIPHER_SENT<br />WOLFSSL MSG: wolfSSL Entering SendFinished<br />WOLFSSL MSG: wolfSSL Leaving SendFinished, return 0<br />WOLFSSL MSG: accept state ACCEPT_FINISHED_DONE<br />WOLFSSL MSG: received record layer msg<br />WOLFSSL MSG: got ALERT!<br />WOLFSSL MSG: Got alert<br />WOLFSSL MSG: wolfSSL error occurred, error = 20<br />WOLFSSL MSG: wolfSSL error occurred, error = -313<br />WOLFSSL MSG: wolfSSL Entering SSL_get_error<br />WOLFSSL MSG: wolfSSL Leaving SSL_get_error, return -313</p><br /><p>What does line &quot;Client attempting to connect with different version&quot; means?</p><p>Any obvious reasons why I would get intermittent Alert 20 messages?</p><p>Any help would be appreciated.</p><p>Thanks</p>]]></description>
			<author><![CDATA[null@example.com (alex2021)]]></author>
			<pubDate>Fri, 29 Oct 2021 22:45:30 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post6339.html#p6339</guid>
		</item>
	</channel>
</rss>
