https://gitlab.synchro.net/main/sbbs/-/commit/ec7f57ab985273580f085bbb
Modified Files:
src/sbbs3/js_socket.c
Log Message:
Close Socket on unhandled TLS errorsWhile errors on transmit seem to be handled well, errors on receivedo not, especially through js_recv_line() which has been seen totrigger a large number (hundreds) of ECONNRESET errors. To preventthis, simply close the socket when an otherwise unhandled erroroccurs.Almost certainly fixes that issue, but the underlying cause is stillundetermined. The calling script (imapservice.js) was checkingSocket.is_connected after each recv_line() call, so if the socketwas actually reset, it would be expected to only call it once.An alternative would be to explicitly handle the error that isseen (CRYPT_ERROR_PARAM1), but let's try a generic fix first and seeof anything breaks because of it. Most likely issue would be aninability to recv() data after calling shutdown(), but I don't thinkmany people do that except to move the TIME_WAIT to where they wantit.
--- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)