Feature: TLS Expiry Notice about cli HOT 3 OPEN

I don't know if we should be warning about these certs, but we can certainly do better than bad cert when the cert is expired.

from cli.

@xealot @dnephin @thaJeztah Is there a PR for this Issue yet? I would love to work on it. Thanks

from cli.

I don't think there's a pull request for this. I think the error that's mentioned here is likely to come from the daemon. The only occurrence of bad certxxx I could find in the daemon / API client code (doing a quick search) is this part; https://github.com/moby/moby/blob/46cdcd206c56172b95ba5c77b827a722dab426c5/client/request.go#L131-L133

if cli.scheme == "https" && strings.Contains(err.Error(), "bad certificate") {
	return serverResp, errors.Wrap(err, "The server probably has client authentication (--tlsverify) enabled. Please check your TLS client certification settings")
}

I'm not sure if bad cert is the only error it returned in this example, or if more information was returned about the certificate having expired

from cli.