Kedar Sovani 87c3decc12 Remove check for would_block in mbedtls ... Basically, in the portability layer, it is checked if the socket is NON-block, and if not, then even the EAGAIN and EWOULDBLOCK errors are diverted to a RECV error. This causes a problem for sockets with receive timeouts set. When such a timeout is set, the condition for NON_BLOCK isn't met and hence a hard error is returned. Searching for EAGAIN and EWOULDBLOCK in lwip returns only 3 results (accept, recvfrom, close) and all of them look to be genuine cases for EWOULDBLOCK. So removing this check to make receive timeout with TLS work.		2019-10-17 16:36:18 +05:30
..
esp32	mbedtls: Remove esp_aes_encrypt/decrypt	2019-09-13 09:44:07 +10:00
include	NimBLE: Add optional mbedTLS support to NimBLE	2019-09-30 14:15:43 +08:00
esp_bignum.c	tools: Mass fixing of empty prototypes (for -Wstrict-prototypes)	2019-08-01 16:28:56 +07:00
esp_hardware.c	mbedtls: import mbedtls project w/o modification	2018-11-27 13:59:26 +08:00
esp_mem.c	mbedtls: import mbedtls project w/o modification	2018-11-27 13:59:26 +08:00
esp_sha1.c	move hwcrypto from esp32 to mbedtls	2019-03-26 16:24:22 +08:00
esp_sha256.c	move hwcrypto from esp32 to mbedtls	2019-03-26 16:24:22 +08:00
esp_sha512.c	move hwcrypto from esp32 to mbedtls	2019-03-26 16:24:22 +08:00
esp_sha.c	esp32: Rewrite esp_sha function	2019-05-13 12:32:45 +08:00
esp_timing.c	Add DTLS support to libcoap using MbedTLS	2019-08-06 10:37:40 +05:30
mbedtls_debug.c	mbedtls: import mbedtls project w/o modification	2018-11-27 13:59:26 +08:00
net_sockets.c	Remove check for would_block in mbedtls	2019-10-17 16:36:18 +05:30