Project

General

Profile

Actions

Bug #12794

closed

Invalid ASN1 from OpenSSL::X509::Requests

Added by cfoo (Chris Foo) over 7 years ago. Updated over 7 years ago.

Status:
Rejected
Assignee:
-
Target version:
-
ruby -v:
ruby 2.3.1p112 (2016-04-26) [x86_64-linux-gnu]
[ruby-core:77431]

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

1.0.1f.out (422 Bytes) 1.0.1f.out Test script output when linked to OpenSSL 1.0.1f cfoo (Chris Foo), 09/27/2016 08:28 PM
1.0.1g.out (458 Bytes) 1.0.1g.out Test script output when linked to OpenSSL 1.0.1g cfoo (Chris Foo), 09/27/2016 08:28 PM
openssl_test.rb (748 Bytes) openssl_test.rb Test script cfoo (Chris Foo), 09/27/2016 08:28 PM
1.0.1u.out (461 Bytes) 1.0.1u.out Test script output when linked to OpenSSL 1.0.1u cfoo (Chris Foo), 09/27/2016 08:59 PM
1.0.2j.out (461 Bytes) 1.0.2j.out Test script output when linked to OpenSSL 1.0.2j cfoo (Chris Foo), 09/27/2016 09:10 PM

Related issues 1 (0 open1 closed)

Is duplicate of Ruby master - Bug #12162: OpenSSL::PKCS7 seems to create broken objects (nested asn.1 error)Third Party's IssueActions
Actions #1

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

Also available in: Atom PDF

Like0
Like0Like0