Home
last modified time | relevance | path

Searched refs:UTCTime (Results 1 – 8 of 8) sorted by relevance

/third_party/node/deps/npm/node_modules/asn1/lib/ber/
Dtypes.js26 UTCTime: 23, property
/third_party/node/deps/npm/node_modules/sshpk/lib/formats/
Dx509.js197 if (der.peek() === asn1.Ber.UTCTime) {
198 return (utcTimeToDate(der.readString(asn1.Ber.UTCTime)));
534 der.writeString(dateToUTCTime(cert.validFrom), asn1.Ber.UTCTime);
535 der.writeString(dateToUTCTime(cert.validUntil), asn1.Ber.UTCTime);
/third_party/openssl/doc/man1/
Dca.pod175 date is YYMMDDHHMMSSZ (the same as an ASN1 UTCTime structure), or
182 date is YYMMDDHHMMSSZ (the same as an ASN1 UTCTime structure), or
751 B<-enddate> and B<-days>) will be encoded as UTCTime if the dates are
/third_party/openssl/doc/man3/
DASN1_generate_nconf.pod80 Encodes an ASN1 B<UTCTime> structure, the value should be in
DASN1_TIME_set.pod138 in RFC5280: if the date can be represented by UTCTime it is used, else
/third_party/mbedtls/tests/suites/
Dtest_suite_x509parse.data1907 X509 CRT ASN1 (GeneralizedTime in notBefore, UTCTime in notAfter)
1911 X509 CRT ASN1 (UTCTime in notBefore, GeneralizedTime in notAfter)
/third_party/openssl/
DCHANGES7352 *) Print out GeneralizedTime and UTCTime in ASN1_STRING_print_ex().
13514 functions. Also ASN1_TIME suite which is a CHOICE of UTCTime or
13516 al: it's just almost always a UTCTime. Note this patch adds new error
/third_party/mbedtls/
DChangeLog4484 * Corrected parsing of UTCTime dates before 1990 and