FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F13.2.0 2019-12-20T19:53:05Z 2019-12-20T19:53:05Z Dimitry Andric dim@FreeBSD.org 2019-12-20T19:53:05Z urn:sha1:0b57cec536236d46e3dba9bd041533462f33dbb7 This uses the new layout of the upstream repository, which was recently migrated to GitHub, and converted into a "monorepo". That is, most of the earlier separate sub-projects with their own branches and tags were consolidated into one top-level directory, and are now branched and tagged together. Updating the vendor area to match this layout is next. 2018-05-19T00:04:01Z Matt Macy mmacy@FreeBSD.org 2018-05-19T00:04:01Z urn:sha1:cccc969bc7f50a0f47f19bb8d195994630a500ea We can't modify vendor code so there's no signal in warnings from it. Similarly -Waddress-of-packed-member is not useful on networking code as access to packed structures is fundamental to its operation. 2018-04-21T02:08:56Z Conrad Meyer cem@FreeBSD.org 2018-04-21T02:08:56Z urn:sha1:3b8d52d3717189ac1172d8e43a5e7397fd003e84 Leave libb2 pristine and silence the warnings for mjg. 2018-03-22T08:32:39Z Li-Wen Hsu lwhsu@FreeBSD.org 2018-03-22T08:32:39Z urn:sha1:bf8e3513bbd411c51e6aa59995b0ef1e45bf55bb Reviewed by: cem Differential Revision: https://reviews.freebsd.org/D14793 2018-03-21T16:18:14Z Conrad Meyer cem@FreeBSD.org 2018-03-21T16:18:14Z urn:sha1:0e33efe4e4b5d24e2d416938af8bc6e6e4160ec8 The upstream repository is on github BLAKE2/libb2. Files landed in sys/contrib/libb2 are the unmodified upstream files, except for one difference: secure_zero_memory's contents have been replaced with explicit_bzero() only because the previous implementation broke powerpc link. Preferential use of explicit_bzero() is in progress upstream, so it is anticipated we will be able to drop this diff in the future. sys/crypto/blake2 contains the source files needed to port libb2 to our build system, a wrapped (limited) variant of the algorithm to match the API of our auth_transform softcrypto abstraction, incorporation into the Open Crypto Framework (OCF) cryptosoft(4) driver, as well as an x86 SSE/AVX accelerated OCF driver, blake2(4). Optimized variants of blake2 are compiled for a number of x86 machines (anything from SSE2 to AVX + XOP). On those machines, FPU context will need to be explicitly saved before using blake2(4)-provided algorithms directly. Use via cryptodev / OCF saves FPU state automatically, and use via the auth_transform softcrypto abstraction does not use FPU. The intent of the OCF driver is mostly to enable testing in userspace via /dev/crypto. ATF tests are added with published KAT test vectors to validate correctness. Reviewed by: jhb, markj Obtained from: github BLAKE2/libb2 Differential Revision: https://reviews.freebsd.org/D14662