Bug #3817: current ruby-openssl impl wrongly utilizes CRYPTO_EX_DATA in X509_STORE

• Status: Closed
• Priority: Normal
• Assignee: -
• Target version: -
• ruby -v: ruby 1.9.3dev

[nahi (Hiroshi Nakamura)]

=begin
cf. http://redmine.ruby-lang.org/issues/show/3000

I think that current ruby-openssl impl wrongly utilizes CRYPTO_EX_DATA in X509_STORE
(I'm not talking about one in X509_STORE_CTX)
=end

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Assigned

=begin

=end

[ko1 (Koichi Sasada)]

How about it?

[nahi (Hiroshi Nakamura)]

• Target version set to 2.0.0

Moved target version to 1.9.x

[nahi (Hiroshi Nakamura)]

• Target version changed from 2.0.0 to 2.6

Postpone this issue again. Let us (nahi and emboss) know if you seem to be bitten by this.

[zzak (Zachary Scott)]

• Assignee changed from nahi (Hiroshi Nakamura) to 7150

[rhenium (Kazuki Yamaguchi)]

• Status changed from Assigned to Closed

This hasn't caused any further issues, and OpenSSL 1.1.0 finally added ex_data functions for X509_STORE. So I think this can be closed now.