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
That's not so easy, because we have to read the first bytes from the socket and then decide, whether it is an unencrypted policy file request or a ssh handshake. This is simple, but, if that first bytes are the ssl handshake, these bytes have to be passed to the ssl application, because that app performs the handshake and expects the handshake data to be available in the read buffer of the socket, but we read them already. I think there are three possible ways of doing it (if we detected, that these bytes are from the ssl handshake)
put these bytes back to the socket buffer, then the ssl app can read them again from the buffer (but there is no [documented] api function for that)
doing the ssl handshake all by ourself (quite complex)
tell the ssl applicatoin to process the handshake data not from the socket, but from us (could work, if it would use the socket in active mode, but is uses it in passive mode)
The text was updated successfully, but these errors were encountered:
That's not so easy, because we have to read the first bytes from the socket and then decide, whether it is an unencrypted policy file request or a ssh handshake. This is simple, but, if that first bytes are the ssl handshake, these bytes have to be passed to the ssl application, because that app performs the handshake and expects the handshake data to be available in the read buffer of the socket, but we read them already. I think there are three possible ways of doing it (if we detected, that these bytes are from the ssl handshake)
The text was updated successfully, but these errors were encountered: