TLS Session Resumption on nRF9160

RE: TLS Session Resumption on nRF9160

Martin Lesund — Mon, 16 Dec 2019 10:36:31 GMT

Hi Tan,

Unfortunately, I cannot comment on when this will be implemented.

I would suggest that you reach out to your Regional Sales Manager with regards to roadmap questions and upcoming features dates.

If you do not know who this is, please send me a direct message on Devzone and I will provide the details.

Best regards,

Martin L.

RE: TLS Session Resumption on nRF9160

eskimo_IcYPaTh — Mon, 16 Dec 2019 02:42:53 GMT

Hi Martin,

Based on that thread, it seems that session caching (or session resumption) has not been fully implemented yet in the bsdlib. Correct me if I'm wrong.

If that's the case, is there an estimated time when this feature will be ready for use?

RE: TLS Session Resumption on nRF9160

Martin Lesund — Fri, 13 Dec 2019 14:48:02 GMT

Please see this thread for more details about this issue.

RE: TLS Session Resumption on nRF9160

Marcus_S — Thu, 28 Nov 2019 10:24:28 GMT

Hi, I have the same problem here. I would like to enable the session cache with setsockopt(). The header net/socket.h does not provide that option. Whereas the header nrf_socket.h defines the option NRF_SO_SEC_SESSION_CACHE with numeric value 3, whis is the same as the numeric value of TLS_CIPHERSUITE_LIST in net/socket.h. So I certainly cannot use this option ID with setsockopt() from net/socket.h, as is will be interpreted as a ciphersuit list. Does this mean that I have to rewrite my application using all the corresponding nrf_socket functions defined in nrf_socket.h instead of the functions defined in net/socket.h? All the SDK samples use net/socket.h, not nrf_socket.h, btw, and in another thead I read that I should use the net/socket functions, which internally use the nrf_socket functions anyway, which makes me wonder why the option definitions are inconsistent.

RE: TLS Session Resumption on nRF9160

eskimo_IcYPaTh — Mon, 17 Jun 2019 10:14:04 GMT

But the struct type 'nrf_sec_config_t' from the header file 'nrf_socket.h' is of a totally different type from the one used in the MQTT example. There is no 'session_cache' variable in the 'mqtt_sec_config' struct.

RE: TLS Session Resumption on nRF9160

Martin Lesund — Thu, 13 Jun 2019 08:46:30 GMT

Hi Tan,

The TLS session cache is disabled by default.
Please see nrf_sec_session_cache_t for details: https://github.com/NordicPlayground/nrfxlib/blob/master/bsdlib/include/nrf_socket.h#L403
note: Session cache, even if enabled may not be used if the peer does not support it.

RE: TLS Session Resumption on nRF9160

eskimo_IcYPaTh — Thu, 13 Jun 2019 02:53:48 GMT

Hi Martin,

My implementation is the same as the example provided. I can get a TLS session going no problems. But not for TLS session resumption.

Edit: I am using the latest modem firmware

RE: TLS Session Resumption on nRF9160

Martin Lesund — Wed, 12 Jun 2019 13:50:29 GMT

Hi Tan,
Please compare your implementation to this MQTT with TLS sample and use the latest modem firmware for the best experience.