From: kitchen@kitchen.io
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91877] [Ruby trunk Feature#9758] Allow setting SSLContext#extra_chain_cert in Net::HTTP
Date: Mon, 18 Mar 2019 22:12:15 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-77145.20190318221215.5a8b3ed7a6d9350a@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-9758.20140418204743@ruby-lang.org
Issue #9758 has been updated by kitchen (Jeremy Kitchen).
I would also love to know about this. I'm running into an issue right now where I'm trying to use ruby (specifically with rest-client, but it's just a wrapper around Net::HTTP) to call out to an API with a client certificate and need a certificate chain to go along with it. The problem is described very well here: https://medium.com/in-the-weeds/net-http-and-x509-client-certificate-chains-and-monkey-patches-oh-my-ea5258dcb697
Thanks!
----------------------------------------
Feature #9758: Allow setting SSLContext#extra_chain_cert in Net::HTTP
https://bugs.ruby-lang.org/issues/9758#change-77145
* 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/
next prev parent reply other threads:[~2019-03-18 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-9758.20140418204743@ruby-lang.org>
2014-04-18 20:47 ` [ruby-core:62090] [ruby-trunk - Bug #9758] [Open] Allow setting SSLContext#extra_chain_cert in Net::HTTP stephen
2015-09-13 3:27 ` [ruby-core:70784] [Ruby trunk - Bug #9758] " zzak
2015-09-13 5:35 ` [ruby-core:70797] [Ruby trunk - Feature " nobu
2018-11-28 17:54 ` [ruby-core:90130] [Ruby trunk Feature#9758] " tristan
2019-03-18 22:12 ` kitchen [this message]
2019-12-09 20:18 ` [ruby-core:96174] [Ruby master " danielc192
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-77145.20190318221215.5a8b3ed7a6d9350a@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).