<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libssl, branch OPENBSD_6_5</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_6_5</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_6_5'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2019-06-07T15:09:44+00:00</updated>
<entry>
<title>MFC libssl fix - rev 1.49 (commitid: DLpHk0vyoFEK0Baa)</title>
<updated>2019-06-07T15:09:44+00:00</updated>
<author>
<name>sthen</name>
<email></email>
</author>
<published>2019-06-07T15:09:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=589c03d1f6136c07954ea6249feb4baa330990a6'/>
<id>urn:sha1:589c03d1f6136c07954ea6249feb4baa330990a6</id>
<content type='text'>
---
Relax parsing of TLS key share extensions on the server.

The RFC does not require X25519 and it also allows clients to send an empty
key share when the want the server to select a group. The current behaviour
results in handshake failures where the client supports TLS 1.3 and sends a
TLS key share extension that does not contain X25519.
---

(this fixes server side in some cases with TLS 1.3 clients with what
would normally be unusual config - however triggered by recent Firefox
packages on Fedora, https://bugzilla.redhat.com/show_bug.cgi?id=1713777)
</content>
</entry>
<entry>
<title>In DTLS, use_srtp is part of the extended server hello while in TLSv1.3,</title>
<updated>2019-05-15T19:25:15+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2019-05-15T19:25:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=f0d432029321083529b36d45280f5308ff8bf24f'/>
<id>urn:sha1:f0d432029321083529b36d45280f5308ff8bf24f</id>
<content type='text'>
it is an encrypted extension.  Include it in the server hello for now.
This will have to be revisited once TLSv1.3 gets there. Fixes SRTP
negotiation.

Problem found by two rust-openssl regress failures reported by mikeb.

with &amp; ok beck

OpenBSD 6.5 errata 002
</content>
</entry>
<entry>
<title>Recommend SSL_CTX_add1_chain_cert(3) rather than</title>
<updated>2019-04-09T22:01:50+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2019-04-09T22:01:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=1e058bee4dd8093d5d6bebd88f82654927d1582c'/>
<id>urn:sha1:1e058bee4dd8093d5d6bebd88f82654927d1582c</id>
<content type='text'>
SSL_CTX_add_extra_chain_cert(3).
From Dr. Stephen Henson &lt;steve at openssl dot org&gt;
via OpenSSL commit a4339ea3 Jan 3 22:38:03 2014 +0000
which is still under a free license.
</content>
</entry>
<entry>
<title>Document SSL_CTX_clear_mode(3) and SSL_clear_mode(3).</title>
<updated>2019-04-09T21:06:31+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2019-04-09T21:06:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=58b03032ff8a03f5c8a1f05dc50a303855755822'/>
<id>urn:sha1:58b03032ff8a03f5c8a1f05dc50a303855755822</id>
<content type='text'>
From Kurt Roeckx &lt;kurt at roeckx dot be&gt;
via OpenSSL commit 57fd5170 May 13 11:24:11 2018 +0200
which is still under a free license.
While here, polish awkward wording and reduce duplication.
</content>
</entry>
<entry>
<title>By design, our state machine is a DAG contrary to the state machine in</title>
<updated>2019-04-05T20:23:38+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2019-04-05T20:23:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=c2876e8ba1959b3e0627d20de447c1449f8294da'/>
<id>urn:sha1:c2876e8ba1959b3e0627d20de447c1449f8294da</id>
<content type='text'>
the spec. To avoid the obvious loop in the RFC's state machine, we added
a CLIENT_HELLO_RETRY state which is a second ClientHello with special
rules.  There is, however, no state to react to this second client hello.
This adds a matching SERVER_HELLO_RETRY state to the handshakes table.

This means in particular that the WITH_HRR state cannot be set in
tls13_server_hello_recv(), so remove this now dead check.

ok jsing
</content>
</entry>
<entry>
<title>Import SSL_CTX_add1_chain_cert(3) from OpenSSL branch 1.1.1, which is still</title>
<updated>2019-04-05T18:29:43+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2019-04-05T18:29:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=a98b4eba250f598d6a0d68257edc1e04e6374565'/>
<id>urn:sha1:a98b4eba250f598d6a0d68257edc1e04e6374565</id>
<content type='text'>
under a free license, omitting functions we don't have and tweaked by me;
the functions were provided by jsing@ in ssl.h rev. 1.166.

While here, also document SSL_CTX_get_extra_chain_certs(3) because
it is closely related to companion functions are already documented
and the API is kind of incomplete without it.
</content>
</entry>
<entry>
<title>Zap two dead #defines that were unused since jsing deleted the</title>
<updated>2019-04-05T05:13:12+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2019-04-05T05:13:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=577d186c707e745daefd41a6fb594038fbebe6d1'/>
<id>urn:sha1:577d186c707e745daefd41a6fb594038fbebe6d1</id>
<content type='text'>
record_type member of the tls13_handshake_action struct.

ok jsing
</content>
</entry>
<entry>
<title>Implement legacy fallback for the TLS 1.3 client.</title>
<updated>2019-04-04T16:53:57+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2019-04-04T16:53:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e827d532c25b674208a351af5d04b7d4513ddaad'/>
<id>urn:sha1:e827d532c25b674208a351af5d04b7d4513ddaad</id>
<content type='text'>
If the Server Hello received indicates that the server did not negotiate
TLS 1.3, fallback to the original TLS client implementation.

ok bcook@, tb@
</content>
</entry>
<entry>
<title>Clean up the cipher/digest table mess.</title>
<updated>2019-04-04T16:44:24+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2019-04-04T16:44:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e08a868e8ded4fb95c7382fe5f5b7d6e9fb4dc23'/>
<id>urn:sha1:e08a868e8ded4fb95c7382fe5f5b7d6e9fb4dc23</id>
<content type='text'>
The original implementation allows for libcrypto to be compiled without a
given algorithm and libssl then detects that ciphers or digests are
unavailable so that it can disable the associated cipher suites.

This is unnecessary since we do not compile out algorithms.

ok beck@, tb@ (a while back)
</content>
</entry>
<entry>
<title>Bump libssl/libtls minors due to symbol addition.</title>
<updated>2019-04-04T15:04:03+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2019-04-04T15:04:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=9d8674ce86c9e527155f720e01047aa6047f0fb7'/>
<id>urn:sha1:9d8674ce86c9e527155f720e01047aa6047f0fb7</id>
<content type='text'>
</content>
</entry>
</feed>
