Add a new item tls_version to call_reporting, containing the OpenSSL version string for the name of the protocol used for the connection.
The test does a normal lookup, but first sets the cipher list to TLS1.3 only ciphers. This will cause a Bad Context error at search time, so we can tell if the underlying OpenSSL library lacks TLS 1.3. The check the call reporting for a TLS version of "TLSv1.3".
Checking for server support for keepalive means we need to know if the server did send a keepalive option to the client. This information is not currently exposed in getdns, so add a flag 'server_keepalive_received' to call_reporting. This is 0 if not received, 1 if received. If received, the actual timeout is in 'idle timeout in ms', though watch out for the overflow alternative.
Suppressing the warning about mapping the 64 bit timeout value to a 32 bit integer,
based on the comments that the "maximum timeout used in practice is 6553500ms." If that
really is the case, we do not need to support 64 bit integers in the dict structure.
- Add OARC servers with pinset only to stubby.conf
- Move Authentication strings to types_internal for use in call_debugging
- Add connection counts to call_debugging
-
that returns all all dnssec replies regardless their status.
When used on its own or in combination with just dnssec_return_status,
it will return BOGUS replies, but those replies will have "dnssec_status": GETDNS_DNSSEC_BOGUS
The response dict "status" will be GETDNS_RESPSTATUS_GOOD then.
When used on in combination with dnssec_return_only_secure,
it will return BOGUS and INSECURE replies (reflected in their "dnssec_status")
The response dict "status" can be any of the status that the dnssec_return_only_secure extenstion returns,
so either GETDNS_RESPSTATUS_GOOD when at least one reply was secure,
GETDNS_RESPSTATUS_NO_SECURE_ANSWERS when all replies were insecure,
or GETDNS_RESPSTATUS_ALL_BOGUS_ANSWERS when all replies were bogus.