Jon Shallow

As this is only locally exploitable (configuration file is in DOS format, not Unix format), can cause the application to crash (but unlikely as it can potentially only read a...

Tag v4.3.4a has been created which includes this PR.

> Would it be possible to support self-signed certificates for TLS (maybe as a runtime option for applications that use > the library)? It's noticed that self-signed certificates are not...

Please try out #1261 to see if this fixes your TCP write issues. As a further comment, on a client, if you set in the `coap_dtls_pki_t->coap_dtls_key_t->coap_pki_key_pem_t` structure the variables `ca_file`,...

PR #1261 has now been merged into the develop branch for testing.

@cyriac83 Can this be closed now?

For PEM based files/memory data, this can include the entire CA chain of multiple certificates (multiple -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE-----) should you require for the CA definition. However, this...

@mkschreder Please see #1267 as a starting point for you to try out, and comments welcome. I am not a Zephyr developer, so there may be some better ways of...

As mentioned previously, 4.3.0 is somewhat old and things have moved on since then, including updates to LwIP. I would recommend you try the latest libcoap develop branch to see...

Thanks for your help troubleshooting here. > But I think mutex is is missing on libcoap for now and you need to fix that. #1181 Raised for this. > error:...