Actions
Bug #12794
closedInvalid ASN1 from OpenSSL::X509::Requests
Status:
Rejected
Assignee:
-
Target version:
-
ruby -v:
ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]
Description
Running #to_der and #to_pem when linked to OpenSSL 1.0.1g+ outputs invalid ASN1. It seems to output valid ASN1 with 1.0.1f. It appears that the last object identifier field is missing in the invalid output. Output from the openssl tools (i.e. openssl req) seems to be valid.
Environment: Ubuntu 16.04.
Files
Updated by rhenium (Kazuki Yamaguchi) over 7 years ago
- Is duplicate of Bug #12162: OpenSSL::PKCS7 seems to create broken objects (nested asn.1 error) added
Updated by rhenium (Kazuki Yamaguchi) over 7 years ago
- Status changed from Open to Rejected
It's not a bug. Calling #to_der against an empty OpenSSL::X509::Request has always returned invalid DER encoding of a CSR, because the mandatory parameters are missing.
It's OpenSSL 1.0.1i that changed the behavior by the way (your 1.0.1g.out shows OpenSSL 1.0.2g, not 1.0.1g).
Actions
Like0
Like0Like0