From: Joseph Jones <joeyi5216@gmail.com>
To: Ruby developers <ruby-core@ruby-lang.org>
Cc: <ruby-core@ruby-lang.org>
Subject: [ruby-core:72345] [Ruby trunk - Bug #11810] [Open] [PATCH] OpenSSL::SSL::SSLcontext#{alpn, npn}_select_cb= does not work properly
Date: Thu, 17 Dec 2015 21:13:26 -0700 [thread overview]
Message-ID: <4F776AAC-720F-401F-B9B8-2E5E2EDC5834@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
Joseph Jones liked your message with Boxer. On December 12, 2015 at 10:34:39 MST, k@rhe.jp wrote:Issue #11810 has been reported by Kazuki Yamaguchi.----------------------------------------Bug #11810: [PATCH] OpenSSL::SSL::SSLcontext#{alpn,npn}_select_cb= does not work properlyhttps://bugs.ruby-lang.org/issues/11810* Author: Kazuki Yamaguchi* Status: Open* Priority: Normal* Assignee: * ruby -v: ruby 2.3.0dev (2015-12-13 trunk 53061) [x86_64-linux]* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN----------------------------------------The protocol list passed to the callback function (set by `SSL_CTX_set_alpn_select_cb`, `SSL_CTX_set_next_proto_select_cb`) is not null-terminated string.This issue seems to have been existing since first NPN was supported (r36871).This patch also removes the code checking the length of protocol name, because it is already validated by OpenSSL.---Files--------------------------------0001-ext-openssl-ossl_ssl.c-ssl_npn_select_cb_common-fix-.patch (1.27 KB)-- https://bugs.ruby-lang.org/
[-- Attachment #2: Type: text/html, Size: 1419 bytes --]
reply other threads:[~2015-12-18 3:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F776AAC-720F-401F-B9B8-2E5E2EDC5834@gmail.com \
--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).