Change the default value of dbms.ssl.policy.*.verify_hostname to true

Author: NataliaIvakina

modules/ROOT/pages/security/ssl-framework.adoc

@@ -269,11 +269,11 @@ The SSL policies are configured by assigning values to parameters of the followi
 | `trusted_dir`          | A directory populated with certificates of trusted parties.                            | `trusted/`
 | `revoked_dir`          | A directory populated with certificate revocation lists (CRLs).                        | `revoked/`
 3+^.^| *Advanced*
-| `verify_hostname`      | Enabling this setting turns on client-side hostname verification.
+| `verify_hostname` footnote:[In Neo4j 2025.01, the default value is changed  from `false` to `true`.]      | Enabling this setting turns on client-side hostname verification.
                            After receiving the server's public certificate, the client compares the
                            address it uses against the certificate Common Name (CN) and Subject Alternative
                            Names (SAN) fields.
-                           If the address does not match those fields, the client disconnects.            | `false`
+                           If the address does not match those fields, the client disconnects.            | `true`
 | `ciphers`              | A comma-separated list of ciphers suites allowed during cipher negotiation.
                            Valid values depend on the current JRE, SSL provider, and TLS version.
                            For Ciphers supported by the Oracle JRE, see the link:https://docs.oracle.com/en/java/javase/17/docs/specs/security/standard-names.html#jsse-cipher-suite-names[Oracle official documentation].