<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ruby.git/test/openssl, branch ruby_2_7</title>
<subtitle>The Ruby Programming Language</subtitle>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/'/>
<entry>
<title>openssl: import v2.1.3</title>
<updated>2021-11-24T07:45:46+00:00</updated>
<author>
<name>Kazuki Yamaguchi</name>
<email>k@rhe.jp</email>
</author>
<published>2021-09-28T06:55:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=e0b323632f5ea07e2646a2ec0b72f56093348265'/>
<id>e0b323632f5ea07e2646a2ec0b72f56093348265</id>
<content type='text'>
Bring the local copy of ruby/openssl in sync with the upstream gem
release v2.1.3. The commits happened in the upstream repository can be
found at:

	https://github.com/ruby/openssl/compare/v2.1.2...v2.1.3

Note that many of these have already been applied to ruby.git and don't
appear in the file changes of this commit.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Bring the local copy of ruby/openssl in sync with the upstream gem
release v2.1.3. The commits happened in the upstream repository can be
found at:

	https://github.com/ruby/openssl/compare/v2.1.2...v2.1.3

Note that many of these have already been applied to ruby.git and don't
appear in the file changes of this commit.
</pre>
</div>
</content>
</entry>
<entry>
<title>test/openssl/test_ssl: skip test_fallback_scsv if necessary</title>
<updated>2020-07-18T04:17:10+00:00</updated>
<author>
<name>Kazuki Yamaguchi</name>
<email>k@rhe.jp</email>
</author>
<published>2020-02-17T08:14:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=0c4d93e6991d365cc77fbaaeae367b9651f2d4cd'/>
<id>0c4d93e6991d365cc77fbaaeae367b9651f2d4cd</id>
<content type='text'>
Run the test case only when the OpenSSL supports both TLS 1.1 and TLS
1.2. Note that the fallback SCSV mechanism is for TLS 1.2 or older and
not for 1.3.

Fixes: https://github.com/ruby/openssl/issues/336
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Run the test case only when the OpenSSL supports both TLS 1.1 and TLS
1.2. Note that the fallback SCSV mechanism is for TLS 1.2 or older and
not for 1.3.

Fixes: https://github.com/ruby/openssl/issues/336
</pre>
</div>
</content>
</entry>
<entry>
<title>OpenSSL 1.1.1 introduces a new '.include' directive. Update our config</title>
<updated>2020-07-11T07:10:41+00:00</updated>
<author>
<name>nagachika</name>
<email>nagachika@ruby-lang.org</email>
</author>
<published>2020-07-11T07:10:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=b4c893a62c71ac28795f8fcefb375131833afd0c'/>
<id>b4c893a62c71ac28795f8fcefb375131833afd0c</id>
<content type='text'>
parser to support that.

As mentioned in the referenced GitHub issue, we should use the OpenSSL
API instead of implementing the parsing logic ourselves, but it will
need backwards-incompatible changes which we can't backport to stable
versions. So continue to use the Ruby implementation for now.

References:
  https://github.com/ruby/openssl/issues/208
  https://github.com/ruby/openssl/pull/216

The original patch was written by Kazuki Yamaguchi &lt;k@rhe.jp&gt; and
the patch for ruby_2_7 branch was prepared by Vít Ondruch.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
parser to support that.

As mentioned in the referenced GitHub issue, we should use the OpenSSL
API instead of implementing the parsing logic ourselves, but it will
need backwards-incompatible changes which we can't backport to stable
versions. So continue to use the Ruby implementation for now.

References:
  https://github.com/ruby/openssl/issues/208
  https://github.com/ruby/openssl/pull/216

The original patch was written by Kazuki Yamaguchi &lt;k@rhe.jp&gt; and
the patch for ruby_2_7 branch was prepared by Vít Ondruch.
</pre>
</div>
</content>
</entry>
<entry>
<title>test/openssl/test_ssl.rb: ignore SSLError when the connection is closed</title>
<updated>2020-03-26T13:17:08+00:00</updated>
<author>
<name>Yusuke Endoh</name>
<email>mame@ruby-lang.org</email>
</author>
<published>2020-03-21T06:46:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=c9a7643a7e5993975e7e8c985df157d73b16a490'/>
<id>c9a7643a7e5993975e7e8c985df157d73b16a490</id>
<content type='text'>
"test_close_after_socket_close" checks if ssl.close is no-op even after
the wrapped socket is closed.  The test itself is fair, but the other
endpoint that is reading the SSL connection may fail with SSLError:
"SSL_read: unexpected eof while reading" in some environments:

https://github.com/ruby/ruby/actions/runs/60085389 (MinGW)
https://rubyci.org/logs/rubyci.s3.amazonaws.com/android28-x86_64/ruby-master/log/20200321T034442Z.fail.html.gz
```
  1) Failure:
OpenSSL::TestSSL#test_close_after_socket_close [D:/a/ruby/ruby/src/test/openssl/utils.rb:299]:
exceptions on 1 threads:
SSL_read: unexpected eof while reading
```

This changeset rescues and ignores the SSLError in the test.

(cherry picked from commit be76e86e69106c6906322dc30aa75c3ff65da63c)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
"test_close_after_socket_close" checks if ssl.close is no-op even after
the wrapped socket is closed.  The test itself is fair, but the other
endpoint that is reading the SSL connection may fail with SSLError:
"SSL_read: unexpected eof while reading" in some environments:

https://github.com/ruby/ruby/actions/runs/60085389 (MinGW)
https://rubyci.org/logs/rubyci.s3.amazonaws.com/android28-x86_64/ruby-master/log/20200321T034442Z.fail.html.gz
```
  1) Failure:
OpenSSL::TestSSL#test_close_after_socket_close [D:/a/ruby/ruby/src/test/openssl/utils.rb:299]:
exceptions on 1 threads:
SSL_read: unexpected eof while reading
```

This changeset rescues and ignores the SSLError in the test.

(cherry picked from commit be76e86e69106c6906322dc30aa75c3ff65da63c)
</pre>
</div>
</content>
</entry>
<entry>
<title>Get rid of false positive misspellings</title>
<updated>2019-12-24T01:33:32+00:00</updated>
<author>
<name>Nobuyoshi Nakada</name>
<email>nobu@ruby-lang.org</email>
</author>
<published>2019-12-24T01:27:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=e954be14d07e54b8dbf71c0fa227e5818eaa01e6'/>
<id>e954be14d07e54b8dbf71c0fa227e5818eaa01e6</id>
<content type='text'>
[Bug #16437]
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[Bug #16437]
</pre>
</div>
</content>
</entry>
<entry>
<title>Fixed misspellings</title>
<updated>2019-12-20T03:19:45+00:00</updated>
<author>
<name>Nobuyoshi Nakada</name>
<email>nobu@ruby-lang.org</email>
</author>
<published>2019-12-20T03:19:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=e68999c82c4863d33a6f893661fba1b7538c5671'/>
<id>e68999c82c4863d33a6f893661fba1b7538c5671</id>
<content type='text'>
Fixed misspellings reported at [Bug #16437], for default gems.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fixed misspellings reported at [Bug #16437], for default gems.
</pre>
</div>
</content>
</entry>
<entry>
<title>Skip very time consuming test [Bug #16196]</title>
<updated>2019-10-10T12:02:45+00:00</updated>
<author>
<name>Nobuyoshi Nakada</name>
<email>nobu@ruby-lang.org</email>
</author>
<published>2019-10-10T12:02:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=c144d7215b3444fa36d28d540b60170a5b30743d'/>
<id>c144d7215b3444fa36d28d540b60170a5b30743d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Slimed down test runtime by stressing openssl.so only [Bug #16196]</title>
<updated>2019-10-10T10:59:21+00:00</updated>
<author>
<name>Nobuyoshi Nakada</name>
<email>nobu@ruby-lang.org</email>
</author>
<published>2019-10-10T10:56:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=0131fab749fb76800de09e49a6abf910201c5b58'/>
<id>0131fab749fb76800de09e49a6abf910201c5b58</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Guard static variable first</title>
<updated>2019-10-10T07:25:28+00:00</updated>
<author>
<name>Nobuyoshi Nakada</name>
<email>nobu@ruby-lang.org</email>
</author>
<published>2019-10-10T07:08:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=203b7fa1ae8cc40d41c38d684f70b3fea7fae813'/>
<id>203b7fa1ae8cc40d41c38d684f70b3fea7fae813</id>
<content type='text'>
* ext/openssl/ossl_asn1.c (Init_ossl_asn1): register the static
  variable to grab an internal object, before creating the object.
  otherwise the just-created object could get collected during the
  global variable list allocation.  [Bug #16196]
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* ext/openssl/ossl_asn1.c (Init_ossl_asn1): register the static
  variable to grab an internal object, before creating the object.
  otherwise the just-created object could get collected during the
  global variable list allocation.  [Bug #16196]
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix keyword argument separation issues in OpenSSL::SSL::SSLSocket#sys{read,write}_nonblock</title>
<updated>2019-09-26T15:01:53+00:00</updated>
<author>
<name>Jeremy Evans</name>
<email>code@jeremyevans.net</email>
</author>
<published>2019-09-25T22:03:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ruby-lang.org/ruby.git/commit/?id=3959469f240edb6c1f43976bbb72a0ba9105a6b1'/>
<id>3959469f240edb6c1f43976bbb72a0ba9105a6b1</id>
<content type='text'>
It's unlikely anyone would actually hit these.  The methods are
private, you only hit this code path if calling these methods
before performing the SSL connection, and there is already a
verbose warning issued.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It's unlikely anyone would actually hit these.  The methods are
private, you only hit this code path if calling these methods
before performing the SSL connection, and there is already a
verbose warning issued.
</pre>
</div>
</content>
</entry>
</feed>
