Open GoogleCodeExporter opened 9 years ago
Here is another one occuring at the same place in the code that is very easy to
reproduce.
Steps to reproduce:
1. Use openfire as server with SSL on 5223
2. Connect using SSL and wrong port 5222 (5223 works correctly of course)
3. jabber-net throws unhandled exception shown below
System.IO.IOException: Authentication failed as remote party has closed the
transport
stream.
bei System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes,
AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer,
AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken
message, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count,
AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[]
buffer, AsyncProtocolRequest asyncRequest)
bei System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
bei System.Net.Security.SslStream.AuthenticateAsClient(String targetHost,
X509CertificateCollection clientCertificates, SslProtocols enabledSslProtocols,
Boolean
checkCertificateRevocation)
bei bedrock.net.AsyncSocket.StartTLS()
ERROR (unbhandled Exception) Terminating?: True Message: System.IO.IOException:
Authentication failed as remote party has closed the transport stream.
bei System.Net.Security.SslState.CheckThrow(Boolean authSucessCheck)
bei System.Net.Security.SslStream.get_RemoteCertificate()
bei bedrock.net.AsyncSocket.get_RemoteCertificate()
bei
jabber.connection.SocketStanzaStream.bedrock.net.ISocketEventListener.OnConnect(
BaseSocket
sock)
bei bedrock.net.AsyncSocket.ExecuteConnect(IAsyncResult ar)
bei System.Net.LazyAsyncResult.Complete(IntPtr userToken)
bei System.Net.ContextAwareResult.CompleteCallback(Object state)
bei System.Threading.ExecutionContext.runTryCode(Object userData)
bei
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(
TryCode
code, CleanupCode backoutCode, Object userData)
bei System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext,
ContextCallback callback, Object state)
bei System.Net.ContextAwareResult.Complete(IntPtr userToken)
bei System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr
userToken)
bei System.Net.Sockets.Socket.ConnectCallback()
bei System.Net.Sockets.Socket.RegisteredWaitCallback(Object state, Boolean timedOut)
bei
System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(Objec
t
state, Boolean timedOut)
Original comment by tilm...@googlemail.com
on 11 Nov 2009 at 3:25
Any news about this?
Original comment by gkoloc...@makingsense.com
on 7 Aug 2013 at 8:25
Any news about this? (2)
Original comment by da...@directip.com.br
on 15 Sep 2014 at 8:26
Original issue reported on code.google.com by
tilm...@googlemail.com
on 11 Nov 2009 at 3:01