• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 578 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.

TLS1.2 MIPs/loading?

radar
Expert 3600 points
Other Parts Discussed in Thread: AM3354

Guys,

So I struggled with if this is a WL18xx or a Sitara question; but I THINK it winds up being an AM335x question (and you can disabuse me of this if required...)

Does the WL18xx SW module support TLS-1.2  when driven with the AM3354 running Linux?  If so, how does that work, is that something built into the module, or something handled in the TCP/IP Stack in Linux? If it would be handled by the AM3354, what kind of drain on the AM3354’s CPU would it impose?

  • 0
    TI__Guru**** 393215 points
    Hi,

    I suggest you post this also on the WiLink forum: e2e.ti.com/.../307 I don't think we have benchmarks for this use case, but I will ask the Crypto experts to check.
  • 0 in reply to Biser Gatchev-XID
    TI__Guru**** 393215 points
    This is the wiki resource for AM335X crypto performance: processors.wiki.ti.com/.../AM335x_Crypto_Performance
  • 0
    TI__Guru** 116770 points

    Hi Radar,

    I haven`t tested connecting to TLS-1.2 with the WL18XX SW module but over Ethernet connection, you can test the connection to TLSv1.2 server using the following openssl command:

    target-evm>openssl
    OpenSSL>s_client -connect <TLS-1.2 supported website>:443

    for Examples
    s_client -connect google.com:443

    The output will show you the certificate from the server and the encryption and hashing algorithms negotiated between the server and the client while establishing the connection.

    If you have enabled crypto drivers in the kernel, the s_client -connect will leverage the AES and SHA drivers to encrypt and hash the messages exchanged from the TLSv1.2 server so the CPU utilitization should be lower than a pure software implementation.

    Regards,
    Rahul


    PS:Check the post for an S_server and s_client connect example that is connecting to TLSv1 server.

    https://e2e.ti.com/support/arm/sitara_arm/f/791/p/457618/1651486#1651486