• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 1192 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3235MODASF: Whether it support TLS 1.3 and WPA3 enterprise

Wenhai Liao (6576188)
Prodigy 170 points
Part Number: CC3235MODASF
Other Parts Discussed in Thread: CC3235SF, CC3301

Dear all,

In datasheet of CC3235MODASF, it describe support fully secured TLS v1.2 and WPA3 personal, I want to know whether it can support TLS v1.3 and WPA3 enterprise.

For TLS v1.3, is there have a plan to show when will support it? If not possible, what is the limitation lead to not support TLS v1.3?

For WPA3 enterprise, could you provide the SDK version that support it, and with an application note to show how to configure/enable it will be more appreciate.

  • 0
    Guru 79905 points

    Hi,

    CC3235SF chips are certified by WiFi alliance to WPA3-EAP. Last year I tested this with OpenWrt router with WPA3-EAP and this security type worked without any issue. Latest SDK (7.10) or older 6.10 should be fine. But there is much bigger issue with WPA-EAP. For WPA-EAP is supported TLS 1.0 only. Because many companies does not allow to use TLS 1.0 any-more, CC3220/CC3235 are not able connect to WPA-EAP networks. According to TI statement TLS 1.2 for EAP cannot be supported due to insufficient memory resources at CC3220/CC3235. I discussed this topic with TI few times and I was never convinced by their arguments. If you want to use CC3220/CC235 for their WPA-EAP feature, I will strongly recommand search for other device (e.g. WiLink-8, CC3301 or devices from competitor manufactures).

    TLS 1.3 for sockets is not supported by network processor itself (NWP). But if you have enough memory resources at your CC3235SF chip, you can run external TLS stack at application processor and enable TLS 1.3 by that way. Latest SKD 7.10 contains example how this can be done. But this approach does not work for WPA-EAP, but only for TLS sockets.

    Jan