<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/lib/libssl/ssl_cert.c, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/lib/libssl/ssl_cert.c?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/lib/libssl/ssl_cert.c?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-06-05T17:55:24Z</updated>
<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>Replace SSL_PKEY_RSA_ENC/SSL_PKEY_RSA_SIGN with SSL_PKEY_RSA.</title>
<updated>2020-05-19T16:35:20Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2020-05-19T16:35:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=169335620533869b7ff0801b3d95964c01249888'/>
<id>urn:sha1:169335620533869b7ff0801b3d95964c01249888</id>
<content type='text'>
Some time prior to SSLeay 0.8.1b, SSL_PKEY_RSA_SIGN got added with the
intention of handling RSA sign only certificates... this incomplete code
had the following comment:

  /* check to see if this is a signing only certificate */
  /* EAY EAY EAY EAY */

And while the comment was removed in 2005, the incomplete RSA sign-only
handling has remained ever since.

Remove SSL_PKEY_RSA_SIGN and rename SSL_PKEY_RSA_ENC to SSL_PKEY_RSA. While
here also remove the unused SSL_PKEY_DH_RSA.

ok tb@
</content>
</entry>
<entry>
<title>s3 is never NULL since s2 (formerly used for SSLv2) does not exist, so there is</title>
<updated>2019-05-15T09:13:16Z</updated>
<author>
<name>bcook</name>
<email>bcook@openbsd.org</email>
</author>
<published>2019-05-15T09:13:16Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=370b96472bf45a8174524306b33a55fc5f360bbc'/>
<id>urn:sha1:370b96472bf45a8174524306b33a55fc5f360bbc</id>
<content type='text'>
no need to check for it. Fixes COV-165788, identified with help from Alex
Bumstead.

ok jsing@
</content>
</entry>
<entry>
<title>Avoid leak in SSL_dup_CA_list()</title>
<updated>2019-04-13T18:04:05Z</updated>
<author>
<name>tb</name>
<email>tb@openbsd.org</email>
</author>
<published>2019-04-13T18:04:05Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8a9e94f30d0d6c0aab8c6ebb72467056aaa7a3e2'/>
<id>urn:sha1:8a9e94f30d0d6c0aab8c6ebb72467056aaa7a3e2</id>
<content type='text'>
In the case that X509_NAME_dup() succeeds, but sk_X509_NAME_push()
fails, name is leaked.  The entire function is trying to be clever
and therefore hard to follow.  Let's do it the stupid but safe way.

ok jsing
</content>
</entry>
<entry>
<title>Strip out all of the pkey to sigalg and sigalg to pkey linkages.</title>
<updated>2019-03-25T17:33:26Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2019-03-25T17:33:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=890365848576c7e95472b62c3f667138bdfa2bc4'/>
<id>urn:sha1:890365848576c7e95472b62c3f667138bdfa2bc4</id>
<content type='text'>
These are no longer used now that we defer signature algorithm selection.

ok beck@
</content>
</entry>
<entry>
<title>Add a chain member to CERT_PKEY and provide functions for manipulating it.</title>
<updated>2019-03-25T16:24:57Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2019-03-25T16:24:57Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=eef9ac4d610696c065ca9225366655883c3d08b9'/>
<id>urn:sha1:eef9ac4d610696c065ca9225366655883c3d08b9</id>
<content type='text'>
Note that this is not the full chain, as the leaf certificate currently
remains in the x509 member of CERT_PKEY. Unfortunately we've got to
contend with the fact that some OpenSSL *_chain_* APIs exclude the leaf
certificate while others include it...

ok beck@ tb@
</content>
</entry>
<entry>
<title>Revert previous - the default sigalg for RSA key exchange is {sha1,rsa}.</title>
<updated>2018-11-19T14:42:01Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2018-11-19T14:42:01Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=0e2b24c4ae669764716dd5627a477daaf0895a8f'/>
<id>urn:sha1:0e2b24c4ae669764716dd5627a477daaf0895a8f</id>
<content type='text'>
In TLSv1.2, if the client does not send a signature algorithms extension
then for RSA key exchange a signature algorithm of {sha1,rsa} is implied.
The MD5+SHA1 hash only applies to older versions of TLS, which do not
support sigalgs.
</content>
</entry>
<entry>
<title>Unbreak legacy ciphers for prior to 1.1 by setting having a legacy</title>
<updated>2018-11-16T02:41:16Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2018-11-16T02:41:16Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=2fab3c323433db3d52cf2f2ccf585a8e4c170640'/>
<id>urn:sha1:2fab3c323433db3d52cf2f2ccf585a8e4c170640</id>
<content type='text'>
sigalg for MD5_SHA1 and using it as the non sigalgs default
ok jsing@
</content>
</entry>
<entry>
<title>Stop keeping track of sigalgs by guessing it from digest and pkey,</title>
<updated>2018-11-10T01:19:09Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2018-11-10T01:19:09Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=fbe97c861da90afbf97f6bd675499438bc709900'/>
<id>urn:sha1:fbe97c861da90afbf97f6bd675499438bc709900</id>
<content type='text'>
just keep the sigalg around so we can remember what we actually
decided to use.
ok jsing@
</content>
</entry>
<entry>
<title>Stop pretending that a cert member in a SSL and SSL_CTX can be NULL.</title>
<updated>2018-11-08T20:55:18Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2018-11-08T20:55:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ac64f7f4b844c5998fb128785cb010f530523944'/>
<id>urn:sha1:ac64f7f4b844c5998fb128785cb010f530523944</id>
<content type='text'>
ok beck@ tb@
</content>
</entry>
</feed>
