A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE 2020-08-30T15:40:20+00:00 2020-08-30T15:40:20+00:00 jsing 2020-08-30T15:40:20+00:00 urn:sha1:5df2cd671a3bb55e3ec34638a6a36eef237c529f This takes the same design/approach used in TLSv1.3 and provides an opaque struct that is self contained and cannot reach back into other layers. For now this just implements/replaces the writing of records for DTLSv1/TLSv1.0/TLSv1.1/TLSv1.2. In doing so we stop copying the plaintext into the same buffer that is used to transmit to the wire. ok inoguchi@ tb@ 2020-03-16T15:25:14+00:00 tb 2020-03-16T15:25:14+00:00 urn:sha1:168e0561df78f7340b3a674c6ffe771fb5b4bbb2 to prefer that. No binary change except in d1_srtp.c where the generated assembly differs only in line numbers (due to a wrapped long line) and in s3_cbc.c where there is no change in the generated assembly. ok inoguchi jsing 2020-03-13T16:40:42+00:00 jsing 2020-03-13T16:40:42+00:00 urn:sha1:591b982ee293938f0df951b42722d3714201a5b8 Like much of the original DTLS code, dtls1_enc() is effectively a renamed copy of tls1_enc(). Since then tls1_enc() has been modified, however the non-AEAD code remains largely the same. As such, remove dtls1_enc() and instead call tls1_enc() from the DTLS code. The tls1_enc() AEAD code does not currently work correctly with DTLS, however this is a non-issue since we do not support AEAD cipher suites with DTLS currently. ok tb@ 2020-03-12T17:09:02+00:00 jsing 2020-03-12T17:09:02+00:00 urn:sha1:090aa8eb50273dd73eaba4ac5362be86b97cd254 Currently the CBC related code stuffs the padding length in the upper bits of the type field... stop doing that and add a padding_length field to the record struct instead. ok inoguchi@ tb@ 2020-03-12T17:01:53+00:00 jsing 2020-03-12T17:01:53+00:00 urn:sha1:63b0f131cbf0e20ff888516045c6693e8515333f SSL3_BUFFER, SSL3_RECORD and DTLS1_RECORD_DATA are currently still in public headers, even though their usage is internal. This moves to using _INTERNAL suffixed versions that are in internal headers, which then allows us to change them without any potential public API fallout. ok inoguchi@ tb@ 2019-05-13T22:48:30+00:00 bcook 2019-05-13T22:48:30+00:00 urn:sha1:076b9689f9bca31fb30753cbb128c6d242db7030 Fixes COV-174858 ok tb@ 2019-02-09T15:26:15+00:00 jsing 2019-02-09T15:26:15+00:00 urn:sha1:bf3fc1487ab4d49b366d075e6f48ee4eef2d29a4 While handshake hash is correct (in as far as it is a hash of handshake messages), using tls1_transcript_hash*() aligns them with the naming of the tls1_transcript*() functions. Additionally, the TLSv1.3 specification uses Transcript-Hash and "transcript hash", which this matches. ok inoguchi@ tb@ 2018-11-08T22:28:52+00:00 jsing 2018-11-08T22:28:52+00:00 urn:sha1:d1a7f20049bf29c61782397cffb632339b12ba54 This provides a cleaner, simpler and more readable API, with code that uses a BUF_MEM instead of a BIO. ok beck@ ("hurry up") and tb@. 2018-10-24T18:04:50+00:00 jsing 2018-10-24T18:04:50+00:00 urn:sha1:c35a1141f368eb454f165541c3dfbe6b6e48b91d In January 2017, we changed large amounts of libssl's data structures to be non-visible/internal, however intentionally left things that the software ecosystem was needing to use. The four or so applications that reached into libssl for record layer related state now implement alternative code. As such, make these data structures internal. ok tb@ 2018-09-08T14:39:41+00:00 jsing 2018-09-08T14:39:41+00:00 urn:sha1:796a6cede5802a1cdee69a9fbb287c26897883f9 ok inoguchi@ tb@