Kedar Sovani 673ccaa1e5 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-12-04 17:28:15 +05:30
..
esp32	Fixed warnings for components driver, esp32 and mbedtls	2019-11-19 15:02:02 +05:30
include	NimBLE: Add optional mbedTLS support to NimBLE (backport)	2019-09-23 21:37:40 +08:00
esp_bignum.c	mbedtls: Fix Z->s in mbedtls_mpi_exp_mod()	2019-06-17 07:19:54 +00: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_sha.c	esp32: Rewrite esp_sha function	2019-05-13 12:32:45 +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
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-12-04 17:28:15 +05:30