wireguard-openbsd/sys/crypto/sha2.c, branch jd/simplify-queueing WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/crypto/sha2.c?h=jd%2Fsimplify-queueing 2015-03-14T03:38:46Z Remove some includes include-what-you-use claims don't 2015-03-14T03:38:46Z jsg jsg@openbsd.org 2015-03-14T03:38:46Z urn:sha1:21dab745d772244ad59a415114e48be2888cfbc8 have any direct symbols used. Tested for indirect use by compiling amd64/i386/sparc64 kernels. ok tedu@ deraadt@ recent changes broke alignment requirements on arm. 2014-12-31T16:56:55Z tedu tedu@openbsd.org 2014-12-31T16:56:55Z urn:sha1:df0156b579dd57f5a1cdcd086473e1ae821f07e2 simplify a bit more, swapping only aligned values and then using memcpy to fill the digest. fix confirmed by jsg. ok jsg kettenis millert as in libc, always assume digest is passed to Final. no null allowed. 2014-12-23T20:40:06Z tedu tedu@openbsd.org 2014-12-23T20:40:06Z urn:sha1:19ec9138c0990e082494b8792d458a1e35a31b22 as in libc, there's no need to check for calling Init on null context 2014-12-23T20:34:41Z tedu tedu@openbsd.org 2014-12-23T20:34:41Z urn:sha1:df3c826f71b4e5a1d03551814d9a1c044c2cf109 use endian.h swap macros instead of home grown versions 2014-12-23T19:21:58Z tedu tedu@openbsd.org 2014-12-23T19:21:58Z urn:sha1:79d4ada2319af7f4e355bf399d12e82227920045 make the code look more like libc by changing Transform to take the state 2014-12-19T17:16:57Z tedu tedu@openbsd.org 2014-12-19T17:16:57Z urn:sha1:ba35811e26e5862ff7e69562727bed4cde23ec54 ok millert convert bcopy/zero to memcpy. ok deraadt djm 2014-12-19T02:50:27Z tedu tedu@openbsd.org 2014-12-19T02:50:27Z urn:sha1:832968b283f1f8c70216a794b8069bef7c1b3ab3 only unroll on i386 and amd64 (where confirmed to be much faster). 2014-12-18T20:29:08Z tedu tedu@openbsd.org 2014-12-18T20:29:08Z urn:sha1:44e3b1d3edb9001661f0ec29c69eddc872c874e3 naddy found sparc64 gets a little slower when unrolled. ok deraadt unroll loops for sha2. quite a bit faster for amd64. 2014-12-17T19:40:24Z tedu tedu@openbsd.org 2014-12-17T19:40:24Z urn:sha1:cde69af7f30f1538102655eab223389f9a876364 ok deraadt millert Defining the interface in terms of char * means most callers are 2014-11-16T17:39:09Z tedu tedu@openbsd.org 2014-11-16T17:39:09Z urn:sha1:de2d0d0b4cbe6369522bc554bb84ec764c7eb996 required to cast their pointers, which is ugly and possibly error prone. accidentally casting an int to a pointer, for example, instead of the address of the int. implicit void * casting is safer. This updates the kernel hash interfaces to use void *. Similar changes are possible for userland. I think it's safe, but there may be some peculiar source compatbility issues there, so let's just do the kernel first. ok dlg millert