handshake

问题 This is the flow I use to setup my HTTPS server with SSL. It works perfectly on Windows, OS X and Ubuntu 13 . But it's failing to work on Ubuntu 14 only and I don't know why. It's not the full code once it's very big, but I can complete with more details if necessary. SSL_library_init(); m_sslContext = SSL_CTX_new( SSLv23_server_method() ); SSL_CTX_use_certificate_chain_file( m_sslContext, "path/to/certificate.crt" ); SSL_CTX_use_PrivateKey_file( m_sslContext, "path/to/privatekey.pem", SSL

问题 In a TLS handshake configured with a client authentication, there is a step where the server receives the client's certificate and choose to trust it or not (for instance, in Java it is done via a TrustManager). I would like to know if the eventual "trust failure" message from the server is sent before or after the server made sure that the client really own that public key (for example, by receiving first some messages from the handshake encoded with the client's private key). The purpose of

问题 I'd like to make an HTTPS connection to a server and, if I'm using non-ephemeral DH key exchange, I'd like to know what the parameters are for that connection. Actually, I don't really care if it's ephemeral or not. What I'm looking for is the ability to make a connection and then warn if the connection is using "weak" DH parameters. Is that something I can check at connection-time? Or is the set of DH parameters (or, more specifically, the length of those parameters, in bits) defined by the

问题 I am trying to validate my website on W3C Nu Html Checker but I am getting below error, don't know why? IO Error: handshake alert: unrecognized_name While my website is working fine on SSL. I tried Handshake alert: unrecognized_name error , but no help. any guidance how to fix this much helpful. I didn't have that much knowledge of server. 来源： https://stackoverflow.com/questions/33580702/w3c-validator-handshake-alert-unrecognized-name

问题 I'm connecting to MSSQL database through my ASP .NET application, but sometimes I got this error while opening connection. Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=3; handshake=14996; To solve it temporarily I've to

问题 I'm connecting to MSSQL database through my ASP .NET application, but sometimes I got this error while opening connection. Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=3; handshake=14996; To solve it temporarily I've to

问题 I'm connecting to a web service which was used before successfully, however now they've changed hostname and sent me two .pem files; one is CA, and other is my new client certificate. (I'm using Java 1.5, Spring + Spring Web Services with Apache httpclient, but I suspect my problem is with certificates, keys and SSL itself.) I've imported both .pem files, as well as host's .crt which I exported from Firefox into my cacerts. However, I'm obviously doing something wrong since I get this

问题 Update : I solved the decoding problem, thanks to pimvdb Follows the solution (in PHP): $len = $masks = $data = $decoded = null; $len = ord ($buffer[1]) & 127; if ($len === 126) { $masks = substr ($buffer, 4, 4); $data = substr ($buffer, 8); } else if ($len === 127) { $masks = substr ($buffer, 10, 4); $data = substr ($buffer, 14); } else { $masks = substr ($buffer, 2, 4); $data = substr ($buffer, 6); } for ($index = 0; $index < strlen ($data); $index++) { $decoded .= $data[$index] ^ $masks[

问题 I'm writing a server which is accepting incoming TCP connections. Let's suppose the server has accepted a TCP connection, and has already received 16 (or so) bytes from the client. Knowing those 16 bytes how can the server detect whether the client wants to initiate an SSL handshake? I've made an experiment, which showed that on my Linux system connecting to localhost (either 127.0.0.1 or AF_UNIX) via SSL makes the client send the following handshake (hexdump), followed by 16 seemingly random

问题 Since 3 days I can't connect to the paypal sandbox. I found out that they maybe dissabled the support for SSLv3. So i tried to change the SSL Version in my curl Request by setting : curl_setopt($curl, CURLOPT_SSLVERSION,1); # 1 = TLSv1 But it still give me the same error : error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure Any idea why the script is still using SSLv3 ? I am using php 5.5 and the following curl version ( currently asking at my hoster [ managed