1 Reply by malik.musovic

(3 replies, posted in wolfSSL)

in our case the ESP WebSocket implementation instructed WolfSSL to not send the whole certificate chain for some reason so we had to change the code in esp_tls_wolfssl.c file

We changed: line 102
if (type == FILE_TYPE_SELF_CERT) {
            if ((*err_ret = wolfSSL_CTX_use_certificate_buffer( (WOLFSSL_CTX *)tls->priv_ctx, cert_buf, cert_len, wolf_fileformat)) == WOLFSSL_SUCCESS) {
                return ESP_OK;
            }

and used wolfSSL_CTX_use_certificate_chain_buffer instead. Then it worked.

Go to forum: wolfSSL

2 Reply by malik.musovic

(3 replies, posted in wolfSSL)

Thanks for the hint!
We will investigate further. If we require further support we will come back.

Go to forum: wolfSSL

3 Topic by malik.musovic

(3 replies, posted in wolfSSL)

Hello I get this error when trying to connect to my host using the right certificates and so on:

E (6674) esp-tls-wolfssl: wolfSSL_connect returned -1, error code: -322
E (6674) esp-tls: Failed to open new connection
E (6684) TRANSPORT_BASE: Failed to open a new connection
E (6694) TRANSPORT_WS: Error connecting to host MYHOST
E (6694) WEBSOCKET_CLIENT: Error transport connect

what does error code: -322 mean exactly?

Go to forum: wolfSSL