This blog post has been created to track all issues related to WICED Wi-Fi security from WICED Studio 5.x onwards. This blog will be updated regularly.




Can't receive the data larger than 1447 bytes in Websocket(tls mode)?-

TLS and azure mqtt broker-

How to use AES-CCM APIs provided in SDK?-

every mqtt connection consume about 8k ram-

wiced_tcp_stream_read issues in WICED 5.2

sdk-5.2.0: snip.https_client test failure

sdk-5.2: mbedtls_open library bug

CYW4307 Cryptography Core

sdk-5.2: wiced_tls_init_identity assertion bug

console: join_ent test peap failure

debugging EAP-TLS on Wiced 3.7.0-3, server-hello failing

Handshake TLS download cert

Open source SSL/TLS Library support for WICED-SDK-3.1.2




Failing Client Authentication with .Net application-

ssl_handshake_client_async freeze at state SSL_CLIENT_CERTIFICATE-

Error: 5035 while TLS connection ?-

TLS Support for both ECC and RSA Certificate/Key pair-

How to change default TLS elliptic curve-


How to know eap_type of enterprise security AP via the scan result?

How correct wifi exploit in sdk3.7 or others?

Snip.websocket_client worked without TLS but doens't work with TLS

DTLS client handshake with WICED Studio 5.0



If there are any other threads on WICED security or BESL library that have remained unresolved, kindly let me know and I will update this blog. Similarly blog posts on other issues will be created if necessary.