¿Cómo depuro problemas de SSL?

How do I debug SSL issues?

To diagnose failures during the application phase, you must decrypt the SSL session using a utility, such as ssldump. You can enable SSL debug logging on the BIG-IP system, test SSL connections for the virtual server using a web browser or the OpenSSL client, and then review the debug log files.

Command-Line Properties for Enabling SSL Debugging

1. The -Djavax. net. debug=all property enables debug logging within the JSSE-based SSL implementation.
2. The -Dssl. debug=true and -Dweblogic. StdoutDebugEnabled=true command-line properties enable debug logging of the SSL calling code within WebLogic Server.

SSL/TLS Logging

1. Open the logging. cfg file in a text editor such as Notepad.
2. Remove the comment next to #log4cplus. logger. SSL=TRACE, and change TRACE to DEBUG.
3. Remove the comment next to #log4cplus. logger. IPAccess=TRACE.

How do I debug SSL handshake, preferably with cURL? I have used this command to troubleshoot client certificate negotiation:

The following contains a list of files that are needed for debugging SSL handshake and configuration issues. Stop IBM HTTP Server. Clear all logs in the install_root/logs directory. If you elect to not clear all of the logs, be sure to remove gsktrace*

Debug TLS handshake using OpenSSL Debug TLS 1.2 with cipher “TLS_RSA_WITH_AES_128_CBC_SHA” This debug provide human readable format for certificates information, ssl process states, and handshake result. OpenSSL cipher string is using different format with IANA.

Each party sends a Finished message under the new algorithm, keys and secrets. The Finished message indicates that the handshake is complete, and the parties may begin to exchange application layer data. This debug provide human readable format for certificates information, ssl process states, and handshake result.