openbsd/src/lib/libssl/t1_lib.c, branch OPENBSD_7_9A mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_92025-12-04T21:16:17+00:00Hook up X25519MKLEM768 to the TLS 1.3 handshake2025-12-04T21:16:17+00:00beck2025-12-04T21:16:17+00:00urn:sha1:dccd1f43a0c2de3852d9515f57353d756629c97a
This does the following:
1) Adds a second key share prediction to the TLS 1.3 handshake.
We only add one as we are unlikely to want to send more than
one PQ one, and one classical one and are unlikely to waste
bytes on a second PQ algorithm (anything that wants something
else that we support can HRR to get it)
2) Adds X25519MLKEM768 (4588) to our list of supported groups.
We add this to our preferred client and server key shares for TLS 1.3
and we now have a separate list for TLS 1.2 which does not do this,
cleaning up the old "full list" from the comments.
3) Updates the golden magic numbers in the regression tests to allow
for the above two things changing the handshake, so the regress
tests pass.
With this you can successfully hybrid PQ with servers and clients
that support it.
ok tb@ kenjiro@
zap weird empty added to tls1_ec_nid2group_id() in previous2025-05-31T15:17:11+00:00tb2025-05-31T15:17:11+00:00urn:sha1:2b916937c9e9b1172e15112ecc352c5eac2a0607Don't use the array index as the group_id2025-05-20T05:39:08+00:00beck2025-05-20T05:39:08+00:00urn:sha1:ea07a243e7c72366afbf4d5e54578f68c061e6e7
This is a precursor to adding new group ids for post quantum
stuff which are up in the 4000 range, so using the array index
as the group id will be silly. Instead we just add the group
id to the structure and we walk the list to find it.
This should never be a very large list for us, so no need
to do anything cuter than linear search for now.
ok jsing@, joshua@
Simplify tls1_check_ec_key()2025-01-18T14:17:05+00:00tb2025-01-18T14:17:05+00:00urn:sha1:9d0a134867a0f5a4df40d59bbd46f54f330d7dea
It doesn't need to have optional arguments anymore, so we can pass
in values and don't need NULL checks and dereferencing.
ok jsing
Rename grp to group like almost everywhere else2025-01-18T13:26:51+00:00tb2025-01-18T13:26:51+00:00urn:sha1:fe34e5ba8e4247027202c49109acc4f00d2d490bRemove parentheses in return statements2025-01-18T13:15:31+00:00tb2025-01-18T13:15:31+00:00urn:sha1:45f18356f473233160d5edf71a56297bf53be91e
ok cc + sha256
Remove two pointless NULL checks2025-01-18T13:11:58+00:00tb2025-01-18T13:11:58+00:00urn:sha1:3e444e4155981c3d065794f0178fdb7a80a5b8e0
The only caller ensures that the EC_KEY is not NULL and passes the address
of comp_id on its stack, so neither will be NULL.
Drop field determination dance2025-01-18T13:07:47+00:00tb2025-01-18T13:07:47+00:00urn:sha1:557d995104dc9e9a0ab79662c8e3ac488cb2d61c
If we get here, we're in a server and have managed to load the cert.
The public key is therefore a point on a built-in curve, and we know
the group is defined over some prime field. Now it is just a matter of
figuring out whether we support the group in libssl.
ok jsing
Stop pretending we support arbirary explicit groups2025-01-18T13:03:02+00:00tb2025-01-18T13:03:02+00:00urn:sha1:7d32176cc7f54fda13623751a9e1b1c349bacb1f
ok jsing
Check for negative EVP_CIPHER_CTX_iv_length() return in libssl2023-11-18T10:51:09+00:00tb2023-11-18T10:51:09+00:00urn:sha1:e72e169bcb8d49d81e9db47f226db4349c4012e3
ok beck