wireguard-openbsd/lib/libssl/bs_cbb.c, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/lib/libssl/bs_cbb.c?h=jd%2Fqueueboosts 2020-03-13T15:54:34Z Ensure that CBB_add_space() always provides zeroed memory. 2020-03-13T15:54:34Z jsing jsing@openbsd.org 2020-03-13T15:54:34Z urn:sha1:df9bd75ecb19a16fa7255e409838e8f7b5f83d6a ok tb@ Use calloc() rather than malloc() when allocating initial CBB buffer. 2020-03-12T17:17:12Z jsing jsing@openbsd.org 2020-03-12T17:17:12Z urn:sha1:ef0fedfaccf6dd69c5711f72eac34852ce3765c4 CBB uses recallocarray() to expand buffers, however was still using malloc() for the initial buffer, which could result in memory being leaked in incorrect use cases. While here also use calloc() to allocate internal structs. ok inoguchi@ tb@ assert.h is often misused. It should not be used in a library 2019-01-23T22:20:40Z beck beck@openbsd.org 2019-01-23T22:20:40Z urn:sha1:59f5034691dd5f1e6477a5fef44165ce5e808939 ok bcook@ jsing@ Provide CBB_add_u32(), as needed for an upcoming conversion. 2018-08-16T18:39:37Z jsing jsing@openbsd.org 2018-08-16T18:39:37Z urn:sha1:bd94b8a5ba71079048f3d3650b2790eaa03c9243 ok tb@ Add CBB_discard_child(), which allows for a child CBB to be discarded. 2017-11-28T16:34:20Z jsing jsing@openbsd.org 2017-11-28T16:34:20Z urn:sha1:e87ff5aee1ed2aa92bbba7775549809876763310 Based on BoringSSL. Clear the child pointer in CBB_cleanup(), so that we have fewer pointers 2017-08-12T02:50:05Z jsing jsing@openbsd.org 2017-08-12T02:50:05Z urn:sha1:9234d803cf1f8edd69c8b69a520341bed495419f hanging around to potentially invalid address space. Discussed with beck@ and doug@ Instead of starting a 'zero-sized' CBB at the size of the first addition 2017-05-07T05:03:41Z jsing jsing@openbsd.org 2017-05-07T05:03:41Z urn:sha1:c99575da5cca28dd1b271ab4a31de8269819ff77 to the CBB, then doubling, start with an initial size of 64 bytes. Almost all uses will exceed this size and we avoid multiple small recallocarray() calls during the initial usage. ok beck@ Use freezero(3) in the CBB clean up path, since this could hold sensitive 2017-04-14T15:20:55Z jsing jsing@openbsd.org 2017-04-14T15:20:55Z urn:sha1:2a6b7f1d923175ad963c8dfa5a8eae46ddf6705a information (such as master keys). Switch CBB to use recallocarray() - this ensures that we do not leak 2017-03-10T15:16:20Z jsing jsing@openbsd.org 2017-03-10T15:16:20Z urn:sha1:42ccf58d43caabf6374c54a28c3cd4478216971f secrets via realloc(). ok inoguchi@ Make it always safe to call CBB_cleanup() providing that CBB_init() or 2015-09-01T13:35:39Z jsing jsing@openbsd.org 2015-09-01T13:35:39Z urn:sha1:28a1f39829e1b83c6944b9ee8f13e8419262b15d CBB_init_fixed() have been attempted. ok doug@