Issue #9758 has been updated by danielc192 (Daniel Cohen).


This change is still blocking X509 certificate presentation with Net::HTTP, specifically when an intermediate certificate is required. The current workaround is to create a mixin for the Net::HTTP module (see the blog post linked in the previous comment), but this isn't a great long term solution. Is there another, less hacky way to solve this?

This issue has been open for nearly 5 years. Other than the patch being outdated, is there a reason this hasn't been merged? I'm happy to update the patch and resubmit, if that's the only obstacle.

Thanks!

----------------------------------------
Feature #9758: Allow setting SSLContext#extra_chain_cert in Net::HTTP
https://bugs.ruby-lang.org/issues/9758#change-83050

* Author: stouset (Stephen Touset)
* Status: Open
* Priority: Normal
* Assignee: openssl
* Target version: 
----------------------------------------
Currently, `Net::HTTP` can only send a single SSL certificate when it
establishes a connection. Some use-cases involve sending an entire
certificate chain to the destination; for this, `SSLContext` supports
assigning to `#extra_chain_cert=`.
    
This adds support in `Net::HTTP` for exposing this underlying `SSLContext`
property to end-users.


---Files--------------------------------
0001-Expose-SSLContext-extra_chain_cert-in-Net-HTTP.patch (1.54 KB)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>