driver / standard (pull_request) Successful in 17s
driver / lint (pull_request) Successful in 20s
driver / types (pull_request) Failing after 1m10s
driver / test (3.12) (pull_request) Successful in 1m14s
driver / test (3.13) (pull_request) Successful in 1m4s
driver / lowest (pull_request) Successful in 38s
driver / build (pull_request) Successful in 34s
driver / security (pull_request) Successful in 1m13s
CI / driver (pull_request) Failing after 3m4s
driver / publish (pull_request) Skipped
Devices ship self-signed certificates, so a driver either fails the CA check on every one of them or turns verification off and sends the login to whatever answers on the address. tls_certificates pins the certificate by its SHA-256 fingerprint instead, shaped like ssh_host_keys: the caller passes the fingerprint to expect by port (optional_args["tls_fingerprints"]), the driver refuses any other certificate before a request carries credentials, and every certificate seen goes to optional_args["tls_certificate_observer"]. Without a fingerprint the first certificate is accepted. CertificateCheck checks the certificate in a handshake of its own, then pins a requests session to it (urllib3's assert_fingerprint, direct and through a proxy), so no other host can step in between the check and the login. Refs NAPALM/napalm-hpe-aruba-procurve#17