Tickets :: Comment on [#270] Android

* Your Email Address
* Spam protection	Enter the letters below: ________ __ _ _ /\ \|___ / \/ \| \| \| \| /\ / \ / /\| \ / \| \| \| \| / \ / /\ \ / / \| \|\/\| \| \| \| \|/ /\ \ / ____ \ / /__\| \| \| \| \|__\| / ____ \ /_/ \_\_____\|_\| \|_\|\____/_/ \_\
Comment	>> Hi, >> >> I'm experiencing issues in a reconnect scenario on Android. We're >> using OpenSSL and connecting to ejabberd. If the device loses >> connection (changes from WIFI -> Cell) and tries to reconnect it >> fails. >> >> In the server logs it results in the following: >> >> :handle_info:194 TLS error = SSL_do_handshake failed: >> error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol >> >> Looking at the code for 1.0.20 it looks like we're still using the >> same SSL object even though we have disconnected and tried to >> connect. In order to try and patch the issue I made a change to the >> disconnect logic to destroy the encryption object. This had the >> desired effect in allowing us to connect once again with the server. >> However I now get a different error. >> >> GLOOX: AREA: 131072, <message from=test@test.com type='error' >> id='2678af4260c9ef376bb893d0c632293424ad01fe00000013'><request >> xmlns='urn:xmpp:receipts'/><error code='406' >> type='modify'><not-acceptable >> xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error><body>123</body></message> >> >> So I'm assuming there is something persistent across sessions. Any >> help would be appreciated. > > So a couple of things were not quite right. On cleanup in > tlsopensslbase.cpp > > I've added: > > void OpenSSLBase::cleanup() > { > if( !m_mutex.trylock() ) > return; > > > if (m_ssl) { > SSL_shutdown(m_ssl); > SSL_clear(m_ssl); > } > > m_secure = false; > m_valid = false; > > m_mutex.unlock(); > } > > Also wasn't setting stream management after disconnect, re-connect > scenario which was causing another issue.
Attachment
Watch this ticket