You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`TRUST_SIGNED_CERTIFICATES` is behaving differently on different platforms. In
order to clean this up we deprecate it and replace with
- `TRUST_SYSTEM_CA_SIGNED_CERTIFICATES` which trusts the system defaults on the
platform
- `TRUST_CUSTOM_CA_SIGNED_CERTIFICATES` which trusts a particular root
certificate (can be a self-signed certificate for example)
* Each time we reconnect to a known host, we verify that its certificate remains the same, guarding against attackers intercepting our communication.
340
362
* <p>
341
363
* Note that this approach is vulnerable to man-in-the-middle attacks the very first time you connect to a new Neo4j instance.
342
-
* If you do not trust the network you are connecting over, consider using {@link #trustSignedBy(File) signed certificates} instead, or manually adding the
364
+
* If you do not trust the network you are connecting over, consider using {@link #trustCustomCertificateSignedBy(File)} signed certificates} instead, or manually adding the
343
365
* trusted host line into the specified file.
344
366
*
345
367
* @param knownHostsFile a file where known certificates are stored.
0 commit comments