Be more wary about OpenSSL not setting errno on error.
OpenSSL will sometimes return SSL_ERROR_SYSCALL without having set
errno; this is apparently a reflection of recv(2)'s habit of not
setting errno when reporting EOF. Ensure that we treat such cases
the same as read EOF. Previously, we'd frequently report them like
"could not accept SSL connection: Success" which is confusing, or
worse report them with an unrelated errno left over from some
previous syscall.
To fix, ensure that errno is zeroed immediately before the call,
and report its value only when it's not zero afterwards; otherwise
report EOF.
For consistency, I've applied the same coding pattern in libpq's
pqsecure_raw_read(). Bare recv(2) shouldn't really return -1 without
setting errno, but in case it does we might as well cope.
Per report from Andres Freund. Back-patch to all supported versions.
Discussion: https://postgr.es/m/20231208181451.deqnflwxqoehhxpe@awork3.anarazel.de
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/ebbd499d4b55c6a6223e01e914308f4a3b936a88
Modified Files
--------------
src/backend/libpq/be-secure-openssl.c | 15 +++++++++++----
src/backend/libpq/pqcomm.c | 22 ++++++++++++++++------
src/interfaces/libpq/fe-secure-openssl.c | 15 +++++++++++----
src/interfaces/libpq/fe-secure.c | 7 +++++++
4 files changed, 45 insertions(+), 14 deletions(-)