Can I force my sensors to ONLY USE TLSv1.2 when probing my devices?
Do some PRTG SSH sensors first attempt to connect using the LEAST SECURE protocol (like SSLv3), and then go higher??? If so, can this behavior be reversed to start at the MOST SECURE protocol (TLSv1.2) and then stop once connected?
Reason I ask: I've got an ES (ElasticSearch) cluster with only TLSv1.2 allowed, and lower protocols (such as TLSv1.1 to SSLv3) disabled. While PRTG successfully connects using TLSv1.2, for some strange reason my ES logs are filled with thousands of messages stating that PRTG attemped to probe (unsuccessfully) using SSLv3, TLSv1, TLSv1.1.....this wastes disk space and (more importantly) makes it hard to scan my logs when issues arise.
I just don't understand why the probes don't start at the most secure protocol first, and then stop one a successful communication is established.
Thanks for any suggestions.