https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112013-03-28T09:08:21ZRuby Issue Tracking SystemRuby master - Bug #8178: OpenSSL::PKCS7::SignerInfohttps://bugs.ruby-lang.org/issues/8178?journal_id=379792013-03-28T09:08:21ZMartinBosslet (Martin Bosslet)Martin.Bosslet@gmail.com
<ul><li><strong>Category</strong> set to <i>ext</i></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>MartinBosslet (Martin Bosslet)</i></li><li><strong>Target version</strong> set to <i>2.1.0</i></li></ul> Ruby master - Bug #8178: OpenSSL::PKCS7::SignerInfohttps://bugs.ruby-lang.org/issues/8178?journal_id=379842013-03-28T09:39:48ZJacob640 (Joseph Coyle)
<ul></ul><p>Because of this bug I have been looking at why it is so difficult to get useful identifying info for pkcs7 signers. I see that OpenSSL provides a utility function to extract a certificate from a pkcs7 message corresponding to a supplied signer info struct called PKCS7_cert_from_signer_info.</p>
<p>Unfortunately due to OpenSSL closely following the pkcs7 data structures SignerInfo structs do not appear to contain the certificate or name of the signing certificate. Because of this PKCS7_cert_from_signer_info requires both a pkcs7 message and a signerInfo struct to provide the signer certificates.</p>
<p>However if we wish to follow the design decisions of OpenSSL it is fairly easy to construct a utility method for OpenSSL::PKCS7 that takes a SignerInfo object and outputs the corresponding certificate. I have written a basic demonstration in this commit: <a href="https://github.com/Jacob640/ruby/commit/10e5f0b74cd08ee23f2b6643a7f86a6dbec857c1" class="external">https://github.com/Jacob640/ruby/commit/10e5f0b74cd08ee23f2b6643a7f86a6dbec857c1</a></p> Ruby master - Bug #8178: OpenSSL::PKCS7::SignerInfohttps://bugs.ruby-lang.org/issues/8178?journal_id=403112013-07-06T07:30:54ZMartinBosslet (Martin Bosslet)Martin.Bosslet@gmail.com
<ul></ul><p>I agree that SignerInfo#name is misleading. It should be easier to get the relevant information, I'll consider your proposal and will think about other ways to improve the API!</p> Ruby master - Bug #8178: OpenSSL::PKCS7::SignerInfohttps://bugs.ruby-lang.org/issues/8178?journal_id=447712014-01-30T06:16:53Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul><li><strong>Target version</strong> changed from <i>2.1.0</i> to <i>2.2.0</i></li></ul> Ruby master - Bug #8178: OpenSSL::PKCS7::SignerInfohttps://bugs.ruby-lang.org/issues/8178?journal_id=541302015-09-13T03:13:42Zzzak (zzak _)
<ul><li><strong>Assignee</strong> changed from <i>MartinBosslet (Martin Bosslet)</i> to <i>7150</i></li></ul> Ruby master - Bug #8178: OpenSSL::PKCS7::SignerInfohttps://bugs.ruby-lang.org/issues/8178?journal_id=805072019-08-08T23:26:49Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Assignee</strong> changed from <i>7150</i> to <i>rhenium (Kazuki Yamaguchi)</i></li></ul><p>I submitted a pull request upstream to remove the <code>OpenSSL::PKCS7::SignerInfo#name</code> method: <a href="https://github.com/ruby/openssl/pull/266" class="external">https://github.com/ruby/openssl/pull/266</a></p> Ruby master - Bug #8178: OpenSSL::PKCS7::SignerInfohttps://bugs.ruby-lang.org/issues/8178?journal_id=805592019-08-10T14:37:43Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Closed</i></li></ul>