A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE 2025-03-09T15:12:18+00:00 2025-03-09T15:12:18+00:00 tb 2025-03-09T15:12:18+00:00 urn:sha1:b8acfd2983c50474382bf8ed132a5b7e7bdedb34 Some people are concerned that leaking a user name is a privacy issue. Allow disabling the __FILE__ and __LINE__ argument in the error stack to avoid this. This can be improved a bit in tree. From Viktor Szakats in https://github.com/libressl/portable/issues/761 ok bcook jsing 2024-09-09T03:32:29+00:00 tb 2024-09-09T03:32:29+00:00 urn:sha1:461979ad807ebd887bb629ba3072f150b5390cd2 This is a small refactoring that wraps a direct call to the record layer's alert_sent() callback into a handler for upcoming reuse in the QUIC code. No functional change. ok jsing 2024-01-27T14:31:01+00:00 jsing 2024-01-27T14:31:01+00:00 urn:sha1:45ebc1fd8bf20df5839902550fef5aeb0e072ec5 2024-01-27T14:23:51+00:00 jsing 2024-01-27T14:23:51+00:00 urn:sha1:9f10df8c2961b5d22fbb67942ef04e74ea843ece This will make it easier to regress test shutdown behaviour in the TLSv1.3 stack. Additionally, `openssl -msg` now shows alerts for TLSv1.3 connections. ok tb@ 2022-07-24T14:28:16+00:00 jsing 2022-07-24T14:28:16+00:00 urn:sha1:2c5937ccb88658c18243c49fc57c58b62e344235 QUIC uses TLS to complete the handshake, however unlike normal TLS it does not use the TLS record layer, rather it provides its own transport. This means that we need to intercept all communication between the TLS handshake and the record layer. This allows TLS handshake message writes to be directed to QUIC, likewise for TLS handshake message reads. Alerts also need to be sent via QUIC, plus it needs to be provided with the traffic keys that are derived by TLS. ok tb@ 2022-07-24T14:16:29+00:00 jsing 2022-07-24T14:16:29+00:00 urn:sha1:8e1be2bf4fabd0e39f3d547284095e5c4610e056 QUIC wants to know what "encryption level" handshake messages should be sent at. Provide an ssl_encryption_level_t enum (via BoringSSL) that defines these (of course quictls decided to make this an OSSL_ENCRYPTION_LEVEL typedef, so provide that as well). Wire these through to tls13_record_layer_set_{read,write}_traffic_key() so that they can be used in upcoming commits. ok tb@ 2022-07-20T06:32:24+00:00 jsing 2022-07-20T06:32:24+00:00 urn:sha1:c883f86bc052054b4a1fc92fd72cc4c7ea17657e There is no way that tls_buffer_set_data() can currently work in conjunction with tls_buffer_expand(). This fact is currently hidden by the way that PHH works, which reads the same data from the record layer (which it needs to do anyway, since we may not have all of the handshake message in a single record). Since this is broken, mop it up and change the PHH callback to not provide the record data. ok beck@ tb@ 2022-07-17T15:49:20+00:00 jsing 2022-07-17T15:49:20+00:00 urn:sha1:aa01620723c4a62e50c3f8ec40f18389e2240ca8 struct tls13_ctx already knows about SSL's and this way tls13_ctx_new() can set up various pointers, rather than duplicating this in tls13_legacy_accept() and tls13_legacy_connect(). ok tb@ 2022-06-03T13:11:04+00:00 tb 2022-06-03T13:11:04+00:00 urn:sha1:932b210d41e3f39b4fa4f872cb281251d94172a8 ok jsing 2022-01-05T17:10:03+00:00 jsing 2022-01-05T17:10:03+00:00 urn:sha1:767ff39662be70f355eac7cf069fd9c23c34580d In preparation to use the key share code in both the TLSv1.3 and legacy stacks, rename tls13_key_share to tls_key_share, moving it into the shared handshake struct. Further changes will then allow the legacy stack to make use of the same code for ephemeral key exchange. ok inoguchi@ tb@