I'm not providing ca certificates so the authentication mode is set to SSL_VERIFY_NONE, however i'm still getting TLS handshake error at ssl_handshake_server_async in wiced_tcp_start_tls when I call wiced_https_get. I have 2 server (Amazon), one in Europe and one in Asia. The Europe one is ok when i access but the Asia one will have TLS handshake error.. Both server is the same (duplicate).
PS. What i don't understand is i'm not storing any ca certificate and i'm sure its set to SSL_VERIFY_NONE. So why does TLS handshake fails? thanks in advance.
Solved! Go to Solution.
If you mean the TLS version from WICED then its right from SDK 2.4.1... I'm not sure what is the TLS version that comes with SDK2.4.1.
looks like everything else is the same but TLS version in server is different, the one that worked is TLS 1.0 while the the one that did not work is using TLS 1.1.
I know I am a little late to the party, but I am encountering the same issue on Wiced SDK version 2.4.0 where SSL_VERIFY_NONE is what is passed in but still there are handshake errors in tcp_start_tls. Is there any fix for this problem other than upgrading to 3.1.x (I would like to avoid that)?