You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently updated sslh and it does not survive for more than a few hours before requiring a restart. Digging into what's happening, it seems that sslh-fork is too strict in handling error-ed accepts():
This led me to a closed pull request #421 and a commit (3117c15) mentioned in its code review.
The commit is odd though, as it is doing exactly the wrong thing the code review mentioned. The committed code can never be reached because CHECK_RES_RETURN(in_socket, "accept", /*void*/ ); would return when in_socket == -1:
I've recently updated sslh and it does not survive for more than a few hours before requiring a restart. Digging into what's happening, it seems that sslh-fork is too strict in handling error-ed accepts():
sslh/sslh-fork.c
Lines 186 to 187 in 710807f
This led me to a closed pull request #421 and a commit (3117c15) mentioned in its code review.
The commit is odd though, as it is doing exactly the wrong thing the code review mentioned. The committed code can never be reached because
CHECK_RES_RETURN(in_socket, "accept", /*void*/ );
would return whenin_socket == -1
:sslh/sslh-fork.c
Lines 186 to 189 in 710807f
Could it be that the commit intended to remove the CHECK_RES_RETURN() as well?
The text was updated successfully, but these errors were encountered: