Error During First Handshake
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 44 Star 314 Fork 104 kontalk/androidclient Code Issues
Error During Websocket Handshake
137 Pull requests 0 Projects 0 Wiki Pulse Graphs New issue error during websocket handshake invalid status line SSL error during first certificate handshake #437 Closed daniele-athome opened this Issue May 28, 2015 · 8 error during websocket handshake 'upgrade' header is missing comments Projects None yet Labels bug wontfix Milestone 3.1.2 Assignees daniele-athome 1 participant Kontalk member daniele-athome commented May 28, 2015 An SSL exception
Error During Websocket Handshake 'sec-websocket-accept' Header Is Missing
happens when sending the verification code (thus the first connection attempt with a client certificate), complaining about a certificate parsing error, but the error text is "Ok"? Probable SSL/TLS version incompatibility (because of Tigase hardened mode?). Error is from a Huawei U8150 with Android 2.2.1. I'll post a stacktrace as soon as I have
Error During Websocket Handshake Unexpected Response Code 301
one. Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. daniele-athome added the bug label May 28, 2015 daniele-athome added this to the 3.0 milestone May 28, 2015 Kontalk member daniele-athome commented May 28, 2015 Probably connected: https://code.google.com/p/android/issues/detail?id=26542 http://stackoverflow.com/questions/9300821/ssl-not-working-on-android-2-2-only-in-2-3 Kontalk member daniele-athome commented May 28, 2015 Please note that certificate chain might be incorrect in fileserver too (Firefox does not detect top level CA). The same happens for XMPP SSL connection, but openssl client seems to detect the chain correctly. Firefox problem? Kontalk member daniele-athome commented Jun 4, 2015 Try again after adding --tls-jdk-nss-bug-workaround-active=true to Tigase configuration. Kontalk member daniele-athome commented Jun 7, 2015 Posted on SO: http://stackoverflow.com/questions/30698087/ssl-error-parsing-the-certificate-ok Kontalk member daniele-athome commented Jun 7, 2015 Notice how desperate I am if I've posted this on SO :-) Kontalk member daniele-athome commented Jun 7, 2015 In the meantime, try parsing the certificate with OpenSSL in C (better if it's the exact version on Android 2.2). daniele-athome self-as
Server Web App Gallery Microsoft Azure Tools Visual Studio Expression Studio Windows Internet Explorer WebMatrix Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums HomeLearnTroubleshootChapter 2. Security IssuesTroubleshooting SSL related issues (Server Certificate) Troubleshooting SSL related issues (Server Certificate) By Kaushal Kumar PandayApril 9, 2012Tools Used in this Troubleshooter: SSLDiag Network Monitor 3.4/Wireshark This material is provided for informational purposes only. Microsoft makes no warranties, express or implied. Overview This document will help you in troubleshooting SSL issues related to IIS only. Client Certificates troubleshooting will not be covered in this document. Server Certificates are meant for Server Authentication and we will be dealing only with Server Certificates in this document. If the Client certificates section is set to “Require” and then you run into issues, then please don’t refer this document. This is meant for troubleshooting SSL Server certificates issue only. It is important to know that every certificate comprises of a public key (used for encryption) and a private key (used for decryption). The private key is known only to the server. The default port for https is 443. I am under the assumption the reader is well-versed in SSL Handshake and the Server Authentication process during the SSL handshake. Description of the Secure Sockets Layer (SSL) Handshake: http://support.microsoft.com/kb/257591 Description of the Server Authentication Process during the SSL Handshake: http://support.microsoft.com/kb/257587 Scenarios The following error message is seen while browsing the website over https: The first thing that has to be checked is whether the website is accessible over http. If yes, then we proceed with our troubleshooting. If not, then you need to have the website working on http first and that's a seperate issue (not covered in this troubleshooter). Now let’s assume the website is accessible over http and we get the above error when trying to browse over https. The problem is seen because the SSL handshake failed and hence the error message was seen. There could be many reasons. We will follow a step-by-step approach to solve this problem. Scenario 1 Check if the server certificate has the private key corresponding to it. Refer the below picture: If private key is missing, then you need to get a certificate containing the private key, which is essentially a .PFX file. There is a command that we could try to run in order to associate