[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35124] [Ruby 1.9-Bug#4374] [ext/openssl] ASN1.decode wrong for infinite length values

From: Martin Bosslet <redmine@...>
Date: 2011-02-06 19:46:53 UTC
List: ruby-core #35124
Issue #4374 has been updated by Martin Bosslet.


I verified that with the current code it's not possible to construct a Constructive 
instance without tagging if the tag_class is passed as an explicit parameter. 
Tagging will be set to :EXPLICIT if it was passed as nil. That's why 

if (infinite && !(tag == V_ASN1_SEQUENCE || tag == V_ASN1_SET)){
                asn1data = rb_funcall(cASN1Constructive,
                                      rb_intern("new"),
                                      4,
                                      value,
                                      INT2NUM(tag),
                                      Qnil,
                                      ID2SYM(tag_class));

in ossl_asn1_decode0 will always produce a Constructive with :EXPLICIT
tagging, and reencoding a parsed ASN.1 value will fail or produce incorrect 
output.
At first I thought changing the defaults in ossl_asn1_initialize would be
more intuitive but not essential to the fix - but now I think it has become
mandatory.
----------------------------------------
http://redmine.ruby-lang.org/issues/show/4374

----------------------------------------
http://redmine.ruby-lang.org

In This Thread

Prev Next