Current HTTPS status.

RE: Current HTTPS status.

isurki — Wed, 13 Nov 2019 17:35:50 GMT

Hi,

Your https sample works perfectly, and now I can send Telegram messages.

I think your sample should be included in Github, it is highly useful.

Best regards.

RE: Current HTTPS status.

Håkon Alseth — Wed, 13 Nov 2019 14:54:36 GMT

I edited my http sample, and added https support, where it connects to google.com:443 and fetches the index.html:

devzone.nordicsemi.com/.../https_5F00_simple_5F00_sample.zip

You can use this as a starting-point (I'll do a PR on it later). Let me know if there's any issues.

*edit* Its up for review now: https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/1488

Kind regards,

Håkon

RE: Current HTTPS status.

Håkon Alseth — Wed, 13 Nov 2019 13:17:41 GMT

Hi,

Unfortunately, we do not have a https sample available.

To use HTTPS, you have to open the socket with IPPROTO_TLS_1_2, and set the socket options (TLS_PEER_VERIFY to '1' is the minimum requirement, rest of setsockopt can be skipped unless you need hostname verification and priv/pub key pair) according to what your needs are, similar to what is done here in the mqtt_transport_tls.c file:

https://github.com/NordicPlayground/fw-nrfconnect-zephyr/blob/master/subsys/net/lib/mqtt/mqtt_transport_socket_tls.c#L21

Or in the download_client.c file:

https://github.com/nordicplayground/fw-nrfconnect-nrf//blob/master/subsys/net/lib/download_client/src/download_client.c#L116

Note that when you set peer_verify to '1' (optional), you can try to skip the sec_tag_list setup (this call https://github.com/nordicplayground/fw-nrfconnect-nrf//blob/master/subsys/net/lib/download_client/src/download_client.c#L82)

PS: port should be 443 for HTTPS.

Kind regards,

Håkon

RE: Current HTTPS status.

Turbo J — Tue, 12 Nov 2019 22:19:02 GMT

The SDK 16.0.0 includes nrf_tls. The mqtt examples seem to use TLS. Note: HTTPS is HTTP over TLS.

Not sure if this is enough, modern HTTPS servers may require some advanced features like SNI (Server Name Indication). Certificate handling would be a real pain on the limited space in an NRF device.

You really don't want to terminate the SSL connection on the small device but on whatever is connected via blueooth (or USB/UART).