From: v.ondruch@tiscali.cz
To: ruby-core@ruby-lang.org
Subject: [ruby-core:90874] [Ruby trunk Bug#15502] Expired certificates in Ruby 2.6.0 test suite
Date: Thu, 03 Jan 2019 16:49:09 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-15502.20190103164908.20ea1e091fc5e827@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15502.20190103164908@ruby-lang.org
Issue #15502 has been reported by vo.x (Vit Ondruch).
----------------------------------------
Bug #15502: Expired certificates in Ruby 2.6.0 test suite
https://bugs.ruby-lang.org/issues/15502
* Author: vo.x (Vit Ondruch)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: REQUIRED
----------------------------------------
There are test failures in Ruby 2.6 such as:
~~~
1) Failure:
FTPTest#test_tls_with_ca_file [/builddir/build/BUILD/ruby-2.6.0/test/net/ftp/test_ftp.rb:1719]:
Exception raised:
<#<OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=error: certificate verify failed (certificate has expired)>>.
~~~
This was fixed in trunk by r66685 and r66686. It would be nice if these could be backported.
It would be even better if the certificates won't expire at all or were regularly updated to prevent this silly issue (test suite of freshly released ruby fails) in the future.
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2019-01-03 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15502.20190103164908@ruby-lang.org>
2019-01-03 16:49 ` v.ondruch [this message]
2019-01-03 16:50 ` [ruby-core:90875] [Ruby trunk Bug#15502][Closed] Expired certificates in Ruby 2.6.0 test suite v.ondruch
2019-01-05 21:34 ` [ruby-core:90905] [Ruby trunk Bug#15502] " naruse
2019-01-09 14:07 ` [ruby-core:90947] " v.ondruch
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.issue-15502.20190103164908.20ea1e091fc5e827@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).