Feature request: a more robust --leap about tlsdate HOT 1 CLOSED

       -l | --leap
              Normally, the passing of time or time yet to  come  ensures  that  SSL  verify  functions  will  fail  to  validate  certificates.  Commonly,
              X509_V_ERR_CERT_NOT_YET_VALID  and  X509_V_ERR_CERT_HAS_EXPIRED  are  painfully annoying but still very important error states. When the only
              issue with the certificates in question is the timing information, this option allows you to trust the remote system's time, as long as it is
              after  RECENT_COMPILE_DATE  and  before  MAX_REASONABLE_TIME.  The  connection  will  only be trusted if X509_V_ERR_CERT_NOT_YET_VALID and/or
              X509_V_OKX509_V_ERR_CERT_HAS_EXPIRED are the only errors encountered. The SSL verify function will not return  X509_V_OK  if  there  are  any
              other  issues, such as self-signed certificates or if the user pins to a CA that is not used by the remote server. This is useful if your RTC
              is broken on boot and you are unable to use DNSEC until you've at least had some kind of leap of cryptographically assured data.