aboutsummaryrefslogtreecommitdiffstats
path: root/socket.c
diff options
context:
space:
mode:
authorMatthias Andree <matthias.andree@gmx.de>2021-11-28 13:03:04 +0100
committerMatthias Andree <matthias.andree@gmx.de>2021-11-28 13:03:04 +0100
commit356b71a1ac60d429d68baf9dea4ad9eb67b50ad9 (patch)
treebde7de13d2cea2b01d4532976f2aa754f99bdb1d /socket.c
parentbe8df128889b202240639a09a6c378da6efe347d (diff)
downloadfetchmail-356b71a1ac60d429d68baf9dea4ad9eb67b50ad9.tar.gz
fetchmail-356b71a1ac60d429d68baf9dea4ad9eb67b50ad9.tar.bz2
fetchmail-356b71a1ac60d429d68baf9dea4ad9eb67b50ad9.zip
Revert "wolfSSL: workaround 5.0.0 SSL_peek() not truly blocking."
This reverts commit 0d32056e7b14bd029aa375f59230a3ad3e2bae51.
Diffstat (limited to 'socket.c')
-rw-r--r--socket.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/socket.c b/socket.c
index eb532655..bb3c1f16 100644
--- a/socket.c
+++ b/socket.c
@@ -521,8 +521,7 @@ int SockRead(int sock, char *buf, int len)
/* SSL_peek says no data... Does he mean no data
or did the connection blow up? If we got an error
then bail! */
- int r = SSL_get_error(ssl, n);
- if (r != 0 && r != SSL_ERROR_WANT_READ) {
+ if (0 != SSL_get_error(ssl, n)) {
return -1;
}
/* We didn't get an error so read at least one