Ethan Atkins db0dfe94d0 FS-9113 [sofia-sip] Clear out ssl error queue
Sofia will unpredictably close a tls transport during call setup. This
occurs when the epoll event loop wakes up the socket reader and SSL_read
returns an error because there is no packet on the socket. Normally
sofia will read the last error using SSL_get_error and return
SSL_ERROR_WANT_READ. Sofia gracefully handles this error and the
transport stays open. Sometimes, however, the worker thread will call
SSL_shutdown for a different transport, which can write an error to the
internal openssl error queue. If that error is not read off the queue,
the next time that SSL_get_error is called, it will read that unrelated
error.

The documentation for SSL_shutdown explains that there are three
possible results -1, 0 and 1 with, oddly, 1 indicating success. The -1
result code occurs when there is no handshake callback registered on the
connection. It can return 0 when there is still work to be done. The
documentation suggest that it is insufficient to call it just once. This
is why I added the do {} while () construct.

Although just the fix to SSL_shutdown was enough to resolve my issue, I
a also audited other calls to SSL_* functions and found a few other
cases where an error may be generated, but was not handled.
2016-04-30 10:39:47 -07:00
..
2014-03-07 18:36:26 -05:00
2014-03-07 18:36:26 -05:00
2014-03-07 18:36:26 -05:00
2014-03-07 18:36:26 -05:00
2016-04-19 20:22:49 +02:00
2014-03-07 18:36:26 -05:00
2015-05-28 12:46:43 -05:00
2014-03-07 18:36:26 -05:00
2014-03-07 18:36:26 -05:00
2014-03-06 00:02:40 +05:00
2010-04-02 01:15:18 -04:00