Wed Jul 12 10:20:15 CST 2023 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.

这是一个关于MySQL SSL连接的警告信息。根据警告信息中提到的要求，如果没有设置明确的选项，则默认情况下必须建立SSL连接。为了与不使用SSL的现有应用程序兼容，verifyServerCertificate属性被设置为'false'。你可以通过设置useSSL=false来显式禁用SSL，或者设置useSSL=true并提供truststore来进行服务器证书验证。

相关问题

CST 2024 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+

CST 2024 WARN 是一个警告信息，它出现的原因是在使用 MySQL 数据库的时候，客户端在建立 SSL 连接时没有对服务器的身份进行验证。这样做是不被推荐的，因为它可能会导致安全问题。

建立 SSL 连接时，客户端会向服务器请求证书以验证其身份。如果客户端没有对证书进行验证，那么可能会遭受中间人攻击。因此，建议在建立 SSL 连接时对服务器的身份进行验证。

为了避免出现 CST 2024 WARN 的警告信息，您可以在建立 SSL 连接时进行服务器身份验证。具体来说，可以使用 MySQL 的 --ssl-mode 参数来设置 SSL 模式，并将其设置为 VERIFY_IDENTITY。这样，当客户端与服务器建立 SSL 连接时，将会对服务器的身份进行验证。

Thu Jun 13 22:42:10 CST 2024 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL

The message you're referring to is a warning in the MySQL logs, specifically related to establishing an SSL (Secure Sockets Layer) connection without verifying the server's identity. Here's what it means:

When you connect to a MySQL server using SSL, it's important to ensure that you are connecting to a trusted server and not an imposter. The warning "Establishing SSL connection without server's identity verification is not recommended" indicates that the client is attempting to establish a secure connection but isn't verifying the authenticity of the server certificate. This could potentially expose your data to man-in-the-middle attacks.

The reasons for this warning are:

1. Security: Verifying the server's identity ensures that you're connecting to the correct database and not an attacker masquerading as the server. It prevents unauthorized access or eavesdropping.

2. Data Integrity: SSL encryption also provides integrity, meaning that data exchanged between the client and server cannot be tampered with if the certificate is genuine.

To address this warning, you should consider these options:
- Obtain and install the server's trusted certificate, if it's missing or out of date.
- Use SSL/TLS configuration settings that enforce client authentication, so both client and server certificates need to be validated.
- Relax the security settings only when connecting to a trusted development or internal network where such verification is unnecessary.

Here are some related questions:

1. What is SSL/TLS and why is it used in MySQL connections?
2. How can I obtain and install a server certificate for my MySQL setup?
3. What are the consequences of ignoring SSL warnings during database interactions?