<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openssl/crypto/objects/obj_lib.c, branch openssl-3.6.4</title>
<subtitle>TLS/SSL and crypto library.</subtitle>
<id>http://git.bktus.com/gpgfrontend/openssl/atom?h=openssl-3.6.4</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/openssl/atom?h=openssl-3.6.4'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/'/>
<updated>2026-06-09T11:44:35Z</updated>
<entry>
<title>Copyright year updates</title>
<updated>2026-06-09T11:44:35Z</updated>
<author>
<name>openssl-machine</name>
<email>openssl-machine@openssl.org</email>
</author>
<published>2026-06-09T11:44:35Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=9ba2cb5f2a0eeb06d4cb88e1b7cc800181053bff'/>
<id>urn:sha1:9ba2cb5f2a0eeb06d4cb88e1b7cc800181053bff</id>
<content type='text'>
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
Reviewed-by: Saša Nedvědický &lt;sashan@openssl.org&gt;
MergeDate: Tue Jun  9 11:44:36 2026
Release: yes
</content>
</entry>
<entry>
<title>Allow 0 length comparisons in OBJ_CMP to return 0 without UB memcmp</title>
<updated>2026-05-06T15:34:54Z</updated>
<author>
<name>Bob Beck</name>
<email>beck@openssl.org</email>
</author>
<published>2026-04-22T18:37:29Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=1e9dfbbad826340e3912157e30cebb2a73e21a31'/>
<id>urn:sha1:1e9dfbbad826340e3912157e30cebb2a73e21a31</id>
<content type='text'>
X509_verify is documented to return -1 if the algorithm is invalid
or can't be compared for any reason.

Sadly this implies that it is legitimate to pass it an incorrect X509
object and it should see this. If we hand it a new X509 object with
nothing filled in, it will memcmp(NULL...) at the end of a stack of
FOO_cmp abstractions, which is UB.

Fix this by permitting the 0 length case to return equal without
a memcmp, as suggested by slontis@ and botovq@

Fixes: https://github.com/openssl/openssl/issues/30922

Reviewed-by: Tomas Mraz &lt;tomas@openssl.foundation&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.foundation&gt;
Reviewed-by: Shane Lontis &lt;shane.lontis@oracle.com&gt;
Reviewed-by: Nikola Pajkovsky &lt;nikolap@openssl.org&gt;
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
MergeDate: Wed May  6 14:55:20 2026
(Merged from https://github.com/openssl/openssl/pull/30943)

(cherry picked from commit ce22d29f5fbeaa976fbc6ab2fc5be7a806142df0)
(cherry picked from commit 09af34b4d905c1b5983ccf0ec45c3931d56deff7)
</content>
</entry>
<entry>
<title>3.6-POST-CLANG-FORMAT-WEBKIT</title>
<updated>2025-12-09T08:00:43Z</updated>
<author>
<name>Bob Beck</name>
<email>beck@openssl.org</email>
</author>
<published>2025-12-09T07:59:00Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=311d0ae130e77cc489e86f630354ff6eadef8d61'/>
<id>urn:sha1:311d0ae130e77cc489e86f630354ff6eadef8d61</id>
<content type='text'>
Reviewed-by: Saša Nedvědický &lt;sashan@openssl.org&gt;
Reviewed-by: Neil Horman &lt;nhorman@openssl.org&gt;
Reviewed-by: Nikola Pajkovsky &lt;nikolap@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/29245)
</content>
</entry>
<entry>
<title>Stop raising ERR_R_MALLOC_FAILURE in most places</title>
<updated>2022-10-05T12:02:03Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2022-09-29T11:57:34Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=e077455e9e57ed4ee4676996b4a9aa11df6327a6'/>
<id>urn:sha1:e077455e9e57ed4ee4676996b4a9aa11df6327a6</id>
<content type='text'>
Since OPENSSL_malloc() and friends report ERR_R_MALLOC_FAILURE, and
at least handle the file name and line number they are called from,
there's no need to report ERR_R_MALLOC_FAILURE where they are called
directly, or when SSLfatal() and RLAYERfatal() is used, the reason
`ERR_R_MALLOC_FAILURE` is changed to `ERR_R_CRYPTO_LIB`.

There were a number of places where `ERR_R_MALLOC_FAILURE` was reported
even though it was a function from a different sub-system that was
called.  Those places are changed to report ERR_R_{lib}_LIB, where
{lib} is the name of that sub-system.
Some of them are tricky to get right, as we have a lot of functions
that belong in the ASN1 sub-system, and all the `sk_` calls or from
the CRYPTO sub-system.

Some extra adaptation was necessary where there were custom OPENSSL_malloc()
wrappers, and some bugs are fixed alongside these changes.

Reviewed-by: Tomas Mraz &lt;tomas@openssl.org&gt;
Reviewed-by: Hugo Landau &lt;hlandau@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/19301)
</content>
</entry>
<entry>
<title>Update copyright year</title>
<updated>2020-11-26T14:18:57Z</updated>
<author>
<name>Matt Caswell</name>
<email>matt@openssl.org</email>
</author>
<published>2020-11-26T14:18:57Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=605856d72cbd4720ad9ccb20c8fd5afbee2ad1a4'/>
<id>urn:sha1:605856d72cbd4720ad9ccb20c8fd5afbee2ad1a4</id>
<content type='text'>
Reviewed-by: Tomas Mraz &lt;tmraz@fedoraproject.org&gt;
(Merged from https://github.com/openssl/openssl/pull/13533)
</content>
</entry>
<entry>
<title>Convert all {NAME}err() in crypto/ to their corresponding ERR_raise() call</title>
<updated>2020-11-13T08:35:02Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2020-11-04T11:23:19Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=9311d0c471ca2eaa259e8c1bbbeb7c46394c7ba2'/>
<id>urn:sha1:9311d0c471ca2eaa259e8c1bbbeb7c46394c7ba2</id>
<content type='text'>
This includes error reporting for libcrypto sub-libraries in surprising
places.

This was done using util/err-to-raise

Reviewed-by: Paul Dale &lt;paul.dale@oracle.com&gt;
(Merged from https://github.com/openssl/openssl/pull/13318)
</content>
</entry>
<entry>
<title>Reorganize private crypto header files</title>
<updated>2019-09-28T18:26:34Z</updated>
<author>
<name>Dr. Matthias St. Pierre</name>
<email>Matthias.St.Pierre@ncp-e.com</email>
</author>
<published>2019-09-27T22:45:33Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=25f2138b0ab54a65ba713c093ca3734d88f7cb51'/>
<id>urn:sha1:25f2138b0ab54a65ba713c093ca3734d88f7cb51</id>
<content type='text'>
Currently, there are two different directories which contain internal
header files of libcrypto which are meant to be shared internally:

While header files in 'include/internal' are intended to be shared
between libcrypto and libssl, the files in 'crypto/include/internal'
are intended to be shared inside libcrypto only.

To make things complicated, the include search path is set up in such
a way that the directive #include "internal/file.h" could refer to
a file in either of these two directoroes. This makes it necessary
in some cases to add a '_int.h' suffix to some files to resolve this
ambiguity:

  #include "internal/file.h"      # located in 'include/internal'
  #include "internal/file_int.h"  # located in 'crypto/include/internal'

This commit moves the private crypto headers from

  'crypto/include/internal'  to  'include/crypto'

As a result, the include directives become unambiguous

  #include "internal/file.h"       # located in 'include/internal'
  #include "crypto/file.h"         # located in 'include/crypto'

hence the superfluous '_int.h' suffixes can be stripped.

The files 'store_int.h' and 'store.h' need to be treated specially;
they are joined into a single file.

Reviewed-by: Richard Levitte &lt;levitte@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/9333)
</content>
</entry>
<entry>
<title>Following the license change, modify the boilerplates in crypto/objects/</title>
<updated>2018-12-06T14:07:30Z</updated>
<author>
<name>Richard Levitte</name>
<email>levitte@openssl.org</email>
</author>
<published>2018-12-06T12:46:38Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=3f870de74ed206631a762a648551adf9c41253a0'/>
<id>urn:sha1:3f870de74ed206631a762a648551adf9c41253a0</id>
<content type='text'>
[skip ci]

Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/7804)
</content>
</entry>
<entry>
<title>Remove parentheses of return.</title>
<updated>2017-10-18T15:05:06Z</updated>
<author>
<name>KaoruToda</name>
<email>kunnpuu@gmail.com</email>
</author>
<published>2017-10-17T14:04:09Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=26a7d938c9bf932a55cb5e4e02abb48fe395c5cd'/>
<id>urn:sha1:26a7d938c9bf932a55cb5e4e02abb48fe395c5cd</id>
<content type='text'>
Since return is inconsistent, I removed unnecessary parentheses and
unified them.

Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
Reviewed-by: Matt Caswell &lt;matt@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/4541)
</content>
</entry>
<entry>
<title>Remove unnecessary #include &lt;openssl/lhash.h&gt; directives.</title>
<updated>2017-09-28T21:38:56Z</updated>
<author>
<name>Pauli</name>
<email>paul.dale@oracle.com</email>
</author>
<published>2017-09-28T21:27:04Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/openssl/commit/?id=f32b0abe26285c6ba2ff258512c08e8f2fbcbdc9'/>
<id>urn:sha1:f32b0abe26285c6ba2ff258512c08e8f2fbcbdc9</id>
<content type='text'>
Reviewed-by: Rich Salz &lt;rsalz@openssl.org&gt;
(Merged from https://github.com/openssl/openssl/pull/4431)
</content>
</entry>
</feed>
