<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libssl/ssl_sigalgs.c, branch OPENBSD_7_9</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2026-03-30T06:20:08+00:00</updated>
<entry>
<title>libssl: announce support for RSASSA-PSS signature schemes</title>
<updated>2026-03-30T06:20:08+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2026-03-30T06:20:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=22f6fa080aa393c2a6455f88e99334d5b461444b'/>
<id>urn:sha1:22f6fa080aa393c2a6455f88e99334d5b461444b</id>
<content type='text'>
Announce the signature schemes for RSASSA-PSS with pubkey OID RSASSA-PSS
between RSASSA-PSS with pubkey OID rsaEncryption and RSASSA-PKCS1-v1_5.

This is the last step in the everlasting saga for making these signature
schemes and certificates with RSASSA-PSS OID work. Fortunately, these are
rarely used since they are extremely complex and inefficient also due to
the large size of the parameters. This addresses bug reports by Steffen
Ullrich and Tom Lane.

Tested by bluhm.

ok djm jsing kenjiro
</content>
</entry>
<entry>
<title>ssl_sigalg_pkey_ok: allow RSASSA-PSS with pubkey OID RSASSA-PSS</title>
<updated>2026-03-30T06:02:21+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2026-03-30T06:02:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=2cce484ddc397481c8dab3c2e72dc77bbefcfddb'/>
<id>urn:sha1:2cce484ddc397481c8dab3c2e72dc77bbefcfddb</id>
<content type='text'>
This fixes a long-standing logic error that hasn't been noticed because
we never announced the rsa_pss_pss_sha{256,384,512} SignatureScheme. The
EVP_PKEY_id() of a RSA-PSS pubkey is EVP_PKEY_RSA_PSS, not EVP_PKEY_RSA.

Thanks to beck for helping me figure out how to fix this correctly. It
drove me nuts for a very long time. Problem also noticed by Tom Lane
due to some PostgreSQL regress failures.

ok djm jsing kenjiro
</content>
</entry>
<entry>
<title>ssl_sigalgs: whitespace tweak</title>
<updated>2026-03-30T05:49:31+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2026-03-30T05:49:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=981fa719b7606cbf7df120993df445357b9b2df7'/>
<id>urn:sha1:981fa719b7606cbf7df120993df445357b9b2df7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Don't push the error stack in ssl_sigalg_select()</title>
<updated>2024-07-09T13:43:57+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2024-07-09T13:43:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=55ebe5358a36bf1d3dfe2b0337ebcd5d479a5d51'/>
<id>urn:sha1:55ebe5358a36bf1d3dfe2b0337ebcd5d479a5d51</id>
<content type='text'>
Doing so breaks certificate selection if a TLS 1.3 client does not support
EC certs, and needs to fall back to RSA.

ok tb@
</content>
</entry>
<entry>
<title>Remove GOST and STREEBOG support from libssl.</title>
<updated>2024-02-03T15:58:34+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2024-02-03T15:58:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=20afa90e552d2efed2187dbafc92170a3895e921'/>
<id>urn:sha1:20afa90e552d2efed2187dbafc92170a3895e921</id>
<content type='text'>
This version of GOST is old and not anywhere close to compliant with
modern GOST standards. It is also very intrusive in libssl and
makes a mess everywhere.  Efforts to entice a suitably minded anyone
to care about it have been unsuccessful.

At this point it is probably best to remove this, and if someone
ever showed up who truly needed a working version, it should be
a clean implementation from scratch, and have it use something
closer to the typical API in libcrypto so it would integrate less
painfully here.

This removes it from libssl in preparation for it's removal from
libcrypto with a future major bump

ok tb@
</content>
</entry>
<entry>
<title>Make internal header file names consistent</title>
<updated>2022-11-26T16:08:57+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-11-26T16:08:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=81d98bf600a381a625eb11b39a725b08c0ba547f'/>
<id>urn:sha1:81d98bf600a381a625eb11b39a725b08c0ba547f</id>
<content type='text'>
Libcrypto currently has a mess of *_lcl.h, *_locl.h, and *_local.h names
used for internal headers. Move all these headers we inherited from
OpenSSL to *_local.h, reserving the name *_internal.h for our own code.
Similarly, move dtls_locl.h and ssl_locl.h to dtls_local and ssl_local.h.
constant_time_locl.h is moved to constant_time.h since it's special.

Adjust all .c files in libcrypto, libssl and regress.

The diff is mechanical with the exception of tls13_quic.c, where
#include &lt;ssl_locl.h&gt; was fixed manually.

discussed with jsing,
no objection bcook
</content>
</entry>
<entry>
<title>Stop using ssl{_ctx,}_security() outside of ssl_seclevel.c</title>
<updated>2022-07-02T16:31:04+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-07-02T16:31:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=274f622e186b69a67b9ccd2ebb48918c3a67ad64'/>
<id>urn:sha1:274f622e186b69a67b9ccd2ebb48918c3a67ad64</id>
<content type='text'>
The API is ugly and we can easily abstract it away. The SSL_SECOP_* stuff
is now confined into ssl_seclevel.c and the rest of the library can make
use of the more straightforward wrappers, which makes it a lot easier on
the eyes.

ok beck jsing
</content>
</entry>
<entry>
<title>Rename uses 'curve' to 'group' and rework tls1 group API.</title>
<updated>2022-07-02T16:00:12+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-07-02T16:00:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=9c3b0c8dc2d9f6d2b9cb9cb675e49a1a04d021b8'/>
<id>urn:sha1:9c3b0c8dc2d9f6d2b9cb9cb675e49a1a04d021b8</id>
<content type='text'>
This reworks various tls1_ curve APIs to indicate success via a boolean
return value and move the output to an out parameter. This makes the
caller code easier and more consistent.

Based on a suggestion by jsing

ok jsing
</content>
</entry>
<entry>
<title>Check sigalg security level when selecting them.</title>
<updated>2022-06-29T07:55:59+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-06-29T07:55:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=6128c9a7f289ea097161a93bb4995b9aee3cfa81'/>
<id>urn:sha1:6128c9a7f289ea097161a93bb4995b9aee3cfa81</id>
<content type='text'>
ok beck jsing
</content>
</entry>
<entry>
<title>Check the security bits of the sigalgs' pkey</title>
<updated>2022-06-29T07:54:54+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2022-06-29T07:54:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=472f5e84ac7bece4d9d62275c2ed47a9084848b8'/>
<id>urn:sha1:472f5e84ac7bece4d9d62275c2ed47a9084848b8</id>
<content type='text'>
ok beck jsing
</content>
</entry>
</feed>
