- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In Wiced 3.7.0-7 it appears that if an EAP-TLS handshake packet is dropped at any stage by the client (Wiced) there is no retry logic in place. Is this a known issue from 3.7.0-7 or later that has been resolved in versions leading to 6.2.1?
Additionally, the release notes are informative for what features have been implemented version to version. Is there a list of bugs that have been resolved version to version?
Solved! Go to Solution.
- Labels:
-
SDK 3.x
-
Security
-
Wifi+Bluetooth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is not a known issue. It is possible that during migration from BESL to mbedTLS, the retry logic would have been added in the mbedTLS library using functions such as mbedtls_ssl_resend() and ssl_resend_hello_request(). But they are used in DTLS.
Basically the list of known issues and bugs is documented in Changelog.txt bundled in WICED SDK. I have attached the same for WICED 6.2.1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is not a known issue. It is possible that during migration from BESL to mbedTLS, the retry logic would have been added in the mbedTLS library using functions such as mbedtls_ssl_resend() and ssl_resend_hello_request(). But they are used in DTLS.
Basically the list of known issues and bugs is documented in Changelog.txt bundled in WICED SDK. I have attached the same for WICED 6.2.1.