<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/x509, branch OPENBSD_7_2</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_7_2</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_7_2'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2023-02-07T15:59:13+00:00</updated>
<entry>
<title>Fix arbitrary memory read in GENERAL_NAME_cmp()</title>
<updated>2023-02-07T15:59:13+00:00</updated>
<author>
<name>bluhm</name>
<email></email>
</author>
<published>2023-02-07T15:59:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=15882269f22f488b8e18605493bb7c0608ab350e'/>
<id>urn:sha1:15882269f22f488b8e18605493bb7c0608ab350e</id>
<content type='text'>
The ASN.1 template for GENERAL_NAME and its corresponding C structure
disagree on the type of the x400Address member. This results in an ASN.1
string to be considered as an ASN.1 type, which allows an attacker to read
(essentially) arbitrary memory. Fix this by forcing comparison as strings.

While the underlying type confusion has been present since time immemorial,
this particular bug came with the EdiPartyName fix (6.8/008_asn1.patch.sig).

Reported by David Benjamin, fix suggested by jsing.

Release date for this was set to be January 31. Unilaterally pushed back to
February 7 by OpenSSL by way of announcement of many completely unrelated
embargoed issues, some of which they had been sitting on since July 2020.

from tb@; OK beck@ jsing@

this is errata/7.2/018_x509.patch.sig
</content>
</entry>
<entry>
<title>Store errors that result from leaf certificate verification.</title>
<updated>2022-10-20T09:45:18+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-10-20T09:45:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=2e08bcb01b2d496908faf5968f289cda7e088285'/>
<id>urn:sha1:2e08bcb01b2d496908faf5968f289cda7e088285</id>
<content type='text'>
In the case that a verification callback is installed that tells the
verifier to continue when a certificate is invalid (e.g. expired),
any error resulting from the leaf certificate verification is not stored
and made available post verification, resulting in an incorrect error being
returned.

Also perform leaf certificate verification prior to adding the chain, which
avoids a potential memory leak (as noted by tb@).

Issue reported by Ilya Shipitsin, who encountered haproxy regress failures.

ok tb@; from jsing

This is errata/7.2/001_x509.patch.sig
</content>
</entry>
<entry>
<title>Prepare to provide OPENSSL_cleanup.</title>
<updated>2022-09-03T17:47:47+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2022-09-03T17:47:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=f1083ba41574ef4e529cc2ea4ff2aa685c4833cd'/>
<id>urn:sha1:f1083ba41574ef4e529cc2ea4ff2aa685c4833cd</id>
<content type='text'>
OPENSSL_cleanup() cleans up and deallocates memory in use by the library.
There are a couple of use cases for this, primarily related to memory
leak testing. This will not be called automatically in LibreSSL, which
means that OpenSSL's OPENSSL_NO_INIT_ATEXIT is implied. If code wants to
clean up then they need to explicitly call this themselves.

ok tb@
</content>
</entry>
<entry>
<title>Switch loop bounds from size_t to int in check_hosts()</title>
<updated>2022-08-31T07:15:31+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-08-31T07:15:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=d232bd6af93b87abffb31bf680b072890c17f61d'/>
<id>urn:sha1:d232bd6af93b87abffb31bf680b072890c17f61d</id>
<content type='text'>
sk_num() can return a negative value, in which case the upper bound is
SIZE_MAX, which results in a very long for loop.

CID 153997

ok jsing
</content>
</entry>
<entry>
<title>Allow empty attribute sets in CSRs</title>
<updated>2022-08-18T16:26:33+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-08-18T16:26:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=8be3e003ec0a654c1538dbd8f7e6d9d965b2e7dc'/>
<id>urn:sha1:8be3e003ec0a654c1538dbd8f7e6d9d965b2e7dc</id>
<content type='text'>
While each attribute must contain at least one extension, it is not
required that a CSR have attributes at all. Instead of signalling an
error by returning NULL if no extensions are found, return an empty
stack of extensions.

Via OpenSSL 1f02ca2d

ok jsing
</content>
</entry>
<entry>
<title>Add missing RCS tag and zap a trailing space</title>
<updated>2022-08-15T11:52:37+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-08-15T11:52:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=726478d55d7f47f50feb22b91bfcb268950310ac'/>
<id>urn:sha1:726478d55d7f47f50feb22b91bfcb268950310ac</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove overly aggressive trust check in legacy verifier that breaks</title>
<updated>2022-08-05T14:46:52+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2022-08-05T14:46:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=33f7a389689c3cc4d7351bfe5ea8496ca7927169'/>
<id>urn:sha1:33f7a389689c3cc4d7351bfe5ea8496ca7927169</id>
<content type='text'>
p5-IO-Socket-SSL regress and regress/sbin/iked/live

Still passes the mutt regress that this was intended to fix.

ok tb@
</content>
</entry>
<entry>
<title>Untangle two logic chains in x509_asid.c into something more readable.</title>
<updated>2022-07-30T17:50:17+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-07-30T17:50:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7004c9ad3ae411f3be9a9af2eb33a5cb6c0fc7d7'/>
<id>urn:sha1:7004c9ad3ae411f3be9a9af2eb33a5cb6c0fc7d7</id>
<content type='text'>
ok jsing
</content>
</entry>
<entry>
<title>Plug leak in X509V3_add1_i2d()</title>
<updated>2022-07-24T21:41:29+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-07-24T21:41:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=eedf40d421c29b605c6fd42b96245296f46aafc4'/>
<id>urn:sha1:eedf40d421c29b605c6fd42b96245296f46aafc4</id>
<content type='text'>
Do not leak the extension that was deleted from the stack.

via OpenSSL c3efe5c9.

ok jsing
</content>
</entry>
<entry>
<title>Remove mkerr.pl remnants from LibreSSL</title>
<updated>2022-07-12T14:42:50+00:00</updated>
<author>
<name>kn</name>
<email></email>
</author>
<published>2022-07-12T14:42:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=89e42d5857196a8071fbafb5565388d0e20ec32b'/>
<id>urn:sha1:89e42d5857196a8071fbafb5565388d0e20ec32b</id>
<content type='text'>
This script is not used at all and files are edited by hand instead.
Thus remove misleading comments incl. the obsolete script/config.

Feedback OK jsing tb
</content>
</entry>
</feed>
