A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE 2025-02-14T12:01:58+00:00 2025-02-14T12:01:58+00:00 jsing 2025-02-14T12:01:58+00:00 urn:sha1:a89810379a758c9cd27af2462547dc646dcfaa61 Currently, SHA{1,256,512}_ASM defines are used to remove the C implementation of sha{1,256,512}_block_data_order() when it is provided by assembly. However, this prevents the C implementation from being used as a fallback. Rename the C sha*_block_data_order() to sha*_block_generic() and provide a sha*_block_data_order() that calls sha*_block_generic(). Replace the Makefile based SHA*_ASM defines with two HAVE_SHA_* defines that allow these functions to be compiled in or removed, such that machine specific verisons can be provided. This should effectively be a no-op on any platform that defined SHA{1,256,512}_ASM. ok tb@ 2024-06-01T07:36:17+00:00 tb 2024-06-01T07:36:17+00:00 urn:sha1:0cd26255605cab2a8643bb8585c4148069240e3c HMAC() and the one-step digests used to support passing a NULL buffer and would return the digest in a static buffer. This design is firmly from the nineties, not thread safe and it saves callers a single line. The few ports that used to rely this were fixed with patches sent to non-hostile (and non-dead) upstreams. It's early enough in the release cycle that remaining uses hidden from the compiler should be caught, at least the ones that matter. There won't be that many since BoringSSL removed this feature in 2017. https://boringssl-review.googlesource.com/14528 Add non-null attributes to the headers and add a few missing bounded attributes. ok beck jsing 2024-03-28T07:06:12+00:00 jsing 2024-03-28T07:06:12+00:00 urn:sha1:40ab5b46122eb72915f2ceb3598d2af6b9accaa9 Replace macros with static inline functions and use names that follow the spec more closely. Unlike SHA256/SHA512, the functions and constants do not align with the number of words loaded, which means we cannot easily loop and just end up just unrolling everything. ok joshua@ tb@ 2024-03-26T12:54:22+00:00 jsing 2024-03-26T12:54:22+00:00 urn:sha1:b77719ed8e84324dfca3cf384b8c08a3f0d310ec Use be32toh(), htobe32() and crypto_{load,store}_htobe32() as appropriate. Also use the same while() loop that is used for other hash functions. ok joshua@ tb@ 2023-08-10T07:15:23+00:00 jsing 2023-08-10T07:15:23+00:00 urn:sha1:13ecebf7d6c58d65f6df008731bbb41f4c2be2f6 This is a hack that is only enabled on a handful of 64 bit platforms, as a workaround for poor compiler optimisation. If you're running an archiac compiler on an archiac architecture, then you can deal with slightly lower performance. ok tb@ 2023-07-08T12:24:10+00:00 beck 2023-07-08T12:24:10+00:00 urn:sha1:f46ac389a5f2c573c854a6c2b50156ca974ea892 ok tb@ 2023-07-08T07:58:25+00:00 jsing 2023-07-08T07:58:25+00:00 urn:sha1:b73d110b33338f5dd55f8edf8a6c9a557c4c5d06 2023-07-08T07:52:25+00:00 jsing 2023-07-08T07:52:25+00:00 urn:sha1:51192ea4c1ff26a1f6ae8dab8e9bb1f465c01aaa 2023-07-08T07:49:45+00:00 jsing 2023-07-08T07:49:45+00:00 urn:sha1:a8e05970851a5ad651999ea1a9e8216dd8f3d06e No change to generated assembly. 2023-07-08T07:43:44+00:00 jsing 2023-07-08T07:43:44+00:00 urn:sha1:69c2702dd169f2187e540d7feaec5a0dabbcaaa3 No functional change.