As far as I can see, that's exactly what needs to happen. An "unexpected message" error should be asserted to the remote end of the connection and to the application, not a complete exit to the operating system.
-Kyle H On 2/18/06, Brad Spencer <[EMAIL PROTECTED]> wrote: > This seems to be due to a bad assumption in d1_pkt.c that assumes only > nice packets can arrive. I've worked up a patch that does _something_ > to handle the error. I am completely unfamiliar with OpenSSL > internals, so I presume someone else can tweak this appropriately :) > My testing seems to show that my change is enough to make the server > resilient to this situation. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
