On Jan 3, 2012, at 11:17 AM, Fredrik Jansson wrote: > Hi all, > > I am having some trouble with DTLS. > > I can easily get into a situation where my server is restarted (or the > client's SSL object is removed for other reasons) and the client may not know. > > Now when the client sends data to the server, a new SSL object is created but > the server is stuck in: > > Info Tue Jan 3 09:55:59 2012 > All.DTLS ssl_info_cb: SSL_accept: error in SSLv3 read client hello B > Info Tue Jan 3 09:55:59 2012 > All.DTLS SSL_read: rc: -1, err: 2 > > i.e. it returns SSL_WANT_READ and of course expects a handshake, but no alert > or similar is sent to the client to indicate the client needs to take some > measure. The client happily keeps sending data. The message should go to the listener and discarded there. If not, it is a problem. > > Any help on how to resolve this would be greatly appreciated. As indicated in my private answer: Your application must detect that the peer is dead. It can do that with its own messages or use DTLS heartbeats for that.
Best regards Michael > > Best regards, > Fredrik Jansson > > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
