ASN1_TIME inconsistent function behaviour / bug?

2003-01-14 Thread Paul Koster
Working on code to read/process and create x509 certificates I encountered the following. The following code results in an ASN1_TIME structure with internal length field of 14 (date1-length =14). date1 = ASN1_TIME_new(); ASN1_GENERALIZEDTIME_set_string(date1, 20020819093712); When

Re: ASN1_TIME inconsistent function behaviour / bug?

2003-01-14 Thread Dr. Stephen Henson
On Tue, Jan 14, 2003, Paul Koster wrote: Working on code to read/process and create x509 certificates I encountered the following. The following code results in an ASN1_TIME structure with internal length field of 14 (date1-length =14). date1 = ASN1_TIME_new();

Re: ASN1_TIME inconsistent function behaviour / bug?

2003-01-14 Thread Paul Koster
The following code results in an ASN1_TIME structure with internal length field of 14 (date1-length =14). date1 = ASN1_TIME_new(); ASN1_GENERALIZEDTIME_set_string(date1, 20020819093712); When extracting time out an existing certificate however with this date/time would result

Re: ASN1_TIME inconsistent function behaviour / bug?

2003-01-14 Thread Dr. Stephen Henson
On Tue, Jan 14, 2003, Paul Koster wrote: The following code results in an ASN1_TIME structure with internal length field of 14 (date1-length =14). date1 = ASN1_TIME_new(); ASN1_GENERALIZEDTIME_set_string(date1, 20020819093712); When extracting time out an existing