<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/lib/libssl, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/lib/libssl?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/lib/libssl?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-06-19T21:26:40Z</updated>
<entry>
<title>We inherited the constant time CBC padding removal from BoringSSL, but</title>
<updated>2020-06-19T21:26:40Z</updated>
<author>
<name>tb</name>
<email>tb@openbsd.org</email>
</author>
<published>2020-06-19T21:26:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=47f04e975a4b111b62acf5a62c889efa5182d30a'/>
<id>urn:sha1:47f04e975a4b111b62acf5a62c889efa5182d30a</id>
<content type='text'>
missed a subsequent fix for an off-by-one in that code.  If the first
byte of a CBC padding of length 255 is mangled, we don't detect that.

Adam Langley's BoringSSL commit 80842bdb44855dd7f1dde64a3fa9f4e782310fc7

Fixes the failing tlsfuzzer lucky 13 test case.

ok beck inoguchi
</content>
</entry>
<entry>
<title>The check_includes step is incorrect dependency management model for</title>
<updated>2020-06-09T16:53:52Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2020-06-09T16:53:52Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4d97159af714fa3a4da75400501d3840d07e13c2'/>
<id>urn:sha1:4d97159af714fa3a4da75400501d3840d07e13c2</id>
<content type='text'>
how our tree gets built.  If this was done in all the libraries (imagine
sys/dev), it would disrupt the development process hugely.  So it should
not be done here either.  use 'make includes' by hand instead.
</content>
</entry>
<entry>
<title>Implement a rolling hash of the ClientHello message, Enforce RFC 8446</title>
<updated>2020-06-06T01:40:08Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2020-06-06T01:40:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=095832a3beabe6679cff4c4b7d27ace9e87b0258'/>
<id>urn:sha1:095832a3beabe6679cff4c4b7d27ace9e87b0258</id>
<content type='text'>
section 4.1.2 to ensure subsequent ClientHello messages after a
HelloRetryRequest messages must be unchanged from the initial
ClientHello.

ok tb@ jsing@
</content>
</entry>
<entry>
<title>Use IANA allocated GOST ClientCertificateTypes.</title>
<updated>2020-06-05T18:14:05Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2020-06-05T18:14:05Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=22c2c18ef388c7340a32bfda6750e2dd2ae7d1ef'/>
<id>urn:sha1:22c2c18ef388c7340a32bfda6750e2dd2ae7d1ef</id>
<content type='text'>
IANA has allocated numbers for GOST ClientCertificateType. Use them in
addition to private values (left in place for compatibility).

Diff from Dmitry Baryshkov &lt;dbaryshkov@gmail.com&gt;

Sponsored by ROSA Linux

ok inoguchi@ tb@
</content>
</entry>
<entry>
<title>Stop sending GOST R 34.10-94 as a CertificateType.</title>
<updated>2020-06-05T17:58:32Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2020-06-05T17:58:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a431b81095a0bbedf91060612e0faa5d2c0cca10'/>
<id>urn:sha1:a431b81095a0bbedf91060612e0faa5d2c0cca10</id>
<content type='text'>
GOST R 34.10-94 is an obsolete certificate type, unsupported by
LibreSSL and by the rest of current software, so there is no point in
sending in the CertificateTypes.

Diff from Dmitry Baryshkov &lt;dbaryshkov@gmail.com&gt;

Sponsored by ROSA Linux

ok inoguchi@ tb@
</content>
</entry>
<entry>
<title>Handle GOST in ssl_cert_dup().</title>
<updated>2020-06-05T17:55:24Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2020-06-05T17:55:24Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c18d223a95aae33f7bc3d38509c6ecc8258e633e'/>
<id>urn:sha1:c18d223a95aae33f7bc3d38509c6ecc8258e633e</id>
<content type='text'>
Add missing case entry for SSL_PKEY_GOST01.

Diff from Dmitry Baryshkov &lt;dbaryshkov@gmail.com&gt;

Sponsored by ROSA Linux

ok inoguchi@ tb@
</content>
</entry>
<entry>
<title>Enable GOST_SIG_FORMAT_RS_LE when verifying certificate signatures.</title>
<updated>2020-06-05T17:53:26Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2020-06-05T17:53:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c2a7ee207bba151810ec11f3f8ecfd436c0b4e80'/>
<id>urn:sha1:c2a7ee207bba151810ec11f3f8ecfd436c0b4e80</id>
<content type='text'>
GOST cipher suites requires that CertVerify signatures be generated in a
special way (see ssl3_send_client_kex_gost(), ssl3_get_cert_verify()).
However, the GOST_SIG_FORMAT_RS_LE flag was not passed in case of TLS 1.2
connections (because they use different code path). Set this flag on
GOST PKEYs.

Diff from Dmitry Baryshkov &lt;dbaryshkov@gmail.com&gt;

Sponsored by ROSA Linux

ok inoguchi@ tb@
</content>
</entry>
<entry>
<title>Align tls13_server_select_certificate() with</title>
<updated>2020-06-04T18:46:21Z</updated>
<author>
<name>tb</name>
<email>tb@openbsd.org</email>
</author>
<published>2020-06-04T18:46:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8121cb119c72f1ba57f0a250dc3121a27bae12d1'/>
<id>urn:sha1:8121cb119c72f1ba57f0a250dc3121a27bae12d1</id>
<content type='text'>
tls13_client_select_certificate().

ok inoguchi
</content>
</entry>
<entry>
<title>Improve client certificate selection for TLSv1.3</title>
<updated>2020-06-04T18:41:42Z</updated>
<author>
<name>tb</name>
<email>tb@openbsd.org</email>
</author>
<published>2020-06-04T18:41:42Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=2414b9ec4b1acff4af2334efd301211ccb859fc3'/>
<id>urn:sha1:2414b9ec4b1acff4af2334efd301211ccb859fc3</id>
<content type='text'>
This allows clients to use EC certificates.

ok inoguchi, jsing
</content>
</entry>
<entry>
<title>mention that TLS_method(3) also supports TLSv1.3;</title>
<updated>2020-06-04T18:06:43Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2020-06-04T18:06:43Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=debbd173b9112f353173e7b152961a043249aa69'/>
<id>urn:sha1:debbd173b9112f353173e7b152961a043249aa69</id>
<content type='text'>
tb@ OKed this part of a larger diff from inoguchi@
</content>
</entry>
</feed>
