MySQL, MariaDB and VillageSQL support the same HammerDB 6.1 connection behaviour for TPROC-C and TPROC-H. To request a one-way encrypted connection when no CA file or client certificates are supplied, enable SSL and leave SSL CApath, SSL CA, SSL Cert and SSL Key empty. HammerDB passes -ssl true to the client library rather than requiring certificate file names.

# Client library option when one-way TLS is enabled with no file paths
-ssl true

This requests TLS encryption but does not, by itself, establish that the server certificate or hostname has been verified. For connections requiring authenticated server identity or mutual TLS, configure the appropriate CA and certificate options and validate the resulting security policy of the chosen database client.

When explicit SSL CApath, CA, certificate or key settings are supplied, HammerDB continues to pass the configured values. Invalid certificate paths now produce a connection/configuration error instead of silently disabling SSL. SSL settings may be changed between connections in the same HammerDB session; changed options are rebuilt, while refreshscript with unchanged settings reuses existing options.

The virtual-user output reports the negotiated SSL cipher when a TLS connection is established. In the GUI use the same SSL connection options during TPROC-C/TPROC-H schema build and driver execution for MySQL, MariaDB or VillageSQL.